Unauthorized customer creation via tokenless GET request
Published Nov 30, 2023 · Updated Jun 5, 2025
Cross-site request forgery in Pimcore Customer Management Framework before 4.0.5 allows remote attackers to create customers via crafted web content. The CustomersController new action accepted a state-changing GET request without validating an anti-CSRF token or request header. Exploitation requires an authenticated administrator to load attacker-controlled content, which submits the request with the administrator session and creates an unauthorized customer record.
Summary
What happened
Cross-site request forgery in Pimcore Customer Management Framework before 4.0.5 allows remote attackers to create customers via crafted web content. The CustomersController new action accepted a state-changing GET request without validating an anti-CSRF token or request header. Exploitation requires an authenticated administrator to load attacker-controlled content, which submits the request with the administrator session and creates an unauthorized customer record.
The record
- CVE
- CVE-2023-49076
- Published
- Nov 30, 2023
- Updated
- Jun 5, 2025
- Vendor
- Pimcore
- Product
- Customer Management Framework
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 30, 2023CVE publishedPublication date reported by the CVE source.
- Jun 5, 2025Record 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=< 4.0.5
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.
Weakness, pattern, technique
Public exploit references
- GHSA customer-creation CSRF proof of conceptproof of concept · demonstrated
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