GHSA-7r35-chv4-xr3r — pimcore/pimcore
Fix: pimcore/pimcore#14721GHSA-7r35-chv4-xr3r is a Cross-site Scripting (XSS) vulnerability in pimcore/pimcore. 1 public exploit reference exists, so weaponization risk is real. A fix is available for pimcore/pimcore — see the affected versions and patch details below.
Pimcore vulnerable to Reflected XSS in Predefined Properties module in Settings
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7r35-chv4-xr3r.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
pimcore/pimcoreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Impact
This vulnerability has the potential to steal a user's cookie and gain unauthorized access to that user's account through the stolen cookie or redirect users to other malicious sites.
Patches
Update to version 10.5.20 or apply this patch manually https://github.com/pimcore/pimcore/pull/14721.patch
Workarounds
Apply https://github.com/pimcore/pimcore/pull/14721.patch manually.
References
https://huntr.dev/bounties/64f943c4-68e5-4ef8-82f6-9c4abe928256/
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | pimcore/pimcore | all versions | 10.5.20composer require pimcore/pimcore:^10.5.20 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pimcore/pimcore, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pimcore/pimcore to 10.5.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7r35-chv4-xr3r is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7r35-chv4-xr3r can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7r35-chv4-xr3r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7r35-chv4-xr3r in your dependencies?
O3 Security finds GHSA-7r35-chv4-xr3r across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.