CVE-2022-3255: pimcore/pimcore · Cross-site Scripting
Affects pimcore/pimcoreSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2022
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 2026-10-25.
What to do
AI-suggested
To mitigate this vulnerability, European organizations should: 1) Monitor Pimcore’s official channels for security patches addressing CVE-2022-3255 and apply updates immediately upon release. 2) Implement strict input validation and output encoding on all user-supplied data within the Pimcore environment to prevent script injection. 3) Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts in browsers. 4) Conduct regular security assessments and penetration testing focused on web application vulnerabilities, including XSS. 5) Educate users and administrators about the risks of phishing and social engineering, as user interaction is required for exploitation. 6) Limit user privileges within Pimcore to the minimum necessary to reduce the impact of compromised accounts. 7) Use web application firewalls (WAFs) configured to detect and block XSS attack patterns targeting Pimcore applications. These measures, combined, will reduce the attack surface and the likelihood of successful exploitation.
Description
If an attacker can control a script that is executed in the victim's browser, then they can typically fully compromise that user. Amongst other things, the attacker can: Perform any action within the application that the user can perform. View any information that the user is able to view. Modify any information that the user is able to modify. Initiate interactions with other application users, including malicious attacks, that will appear to originate from the initial victim user.