VulnerabilityPublished 30 Nov 2023Updated 5 Jun 2025

CVE-2023-49076: pimcore customer-data-framework · Cross-Site Request Forgery (CSRF)

Affects pimcore customer-data-frameworkSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 4.0.5 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.0.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade pimcore/customer-data-framework to 4.0.5.

Affected software

Product	Affected	Fixed in
GitHubpimcore/customer-data-framework`pkg:github/pimcore/customer-data-framework`Other threats	Affected <4.0.5	Fixed in 4.0.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their Pimcore customer-data-framework version and upgrade to version 4.0.5 or later to apply the official patch that introduces CSRF protections. In addition to patching, organizations should implement the following practical measures: 1) Conduct a thorough audit of customer data to identify and remove any suspicious or unauthorized entries created before patching; 2) Implement web application firewalls (WAFs) with rules to detect and block CSRF attack patterns; 3) Educate users and administrators about the risks of CSRF and encourage cautious behavior regarding unsolicited links or sites while authenticated; 4) Review and enhance session management and authentication mechanisms to limit the impact of CSRF attacks; 5) Monitor logs for unusual customer creation activities that could indicate exploitation attempts; 6) Consider deploying Content Security Policy (CSP) headers and SameSite cookie attributes to reduce CSRF risks further. These steps, combined with patching, will reduce the attack surface and improve resilience against CSRF threats.

Description

Customer-data-framework allows management of customer data within Pimcore. There are no tokens or headers to prevent CSRF attacks from occurring, therefore an attacker could abuse this vulnerability to create new customers. This issue has been patched in version 4.0.5.

Impact

For European organizations using Pimcore’s customer-data-framework, this vulnerability could lead to unauthorized creation of customer records, potentially polluting customer databases with fraudulent or malicious entries. This can degrade data integrity, complicate customer management processes, and potentially facilitate further attacks such as phishing or social engineering if attackers insert deceptive customer data. While the vulnerability does not directly expose sensitive data or disrupt availability, the integrity compromise can undermine trust in customer data and lead to operational inefficiencies. Organizations in sectors with strict data governance and compliance requirements (e.g., finance, healthcare, retail) may face regulatory scrutiny if data integrity is compromised. Additionally, attackers could use this vulnerability as a foothold to escalate attacks or conduct fraud schemes leveraging the manipulated customer data.

Summary

CVE-2023-49076 is a medium-severity vulnerability classified as CWE-352, a Cross-Site Request Forgery (CSRF) issue affecting the customer-data-framework component of Pimcore, a platform used for managing customer data. The vulnerability exists because the affected versions of the customer-data-framework (all versions prior to 4.0.5) do not implement anti-CSRF tokens or headers to validate the authenticity of requests. This lack of protection allows an attacker to craft malicious web requests that, when executed by an authenticated user’s browser, can perform unauthorized actions such as creating new customer records without the user’s consent. The vulnerability requires user interaction (the victim must be authenticated and visit a malicious site or click a crafted link), but does not require any privileges or authentication on the attacker’s part. The CVSS 3.1 score is 4.3 (medium), reflecting that the impact is limited to integrity (unauthorized creation of customer data) without affecting confidentiality or availability. The vulnerability has been addressed in Pimcore customer-data-framework version 4.0.5, where proper CSRF protections have been implemented. No known exploits are currently reported in the wild, but the vulnerability poses a risk to organizations using vulnerable versions of this framework.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 09:42 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats