Default card-token modification via missing nonce validation
Published Feb 28, 2024 · Updated Apr 8, 2026
CSRF in Fabrick S.p.A. Ecommerce Fabrick 20221130 and earlier allows remote attackers to change a user's default payment-card token. The ajax_set_default_card handler accepts a card token and writes it as the user's default without validating a WordPress nonce. Exploitation requires an administrator with an authenticated browser session to act on a forged request, and the bounded consequence is modification of the stored default card token.
Summary
What happened
CSRF in Fabrick S.p.A. Ecommerce Fabrick 20221130 and earlier allows remote attackers to change a user's default payment-card token. The ajax_set_default_card handler accepts a card token and writes it as the user's default without validating a WordPress nonce. Exploitation requires an administrator with an authenticated browser session to act on a forged request, and the bounded consequence is modification of the stored default card token.
The record
- CVE
- CVE-2024-0431
- Published
- Feb 28, 2024
- Updated
- Apr 8, 2026
- Vendor
- Fabrick S.p.A.
- Product
- Ecommerce Fabrick
- Classifications
- CWE-352, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 28, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=20221130
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo