GHSA-6hh6-59j2-qrxw — silverstripe/cms
MEDIUMGHSA-6hh6-59j2-qrxw is a medium-severity (CVSS 6.1) vulnerability in silverstripe/cms. A fix is available for silverstripe/cms — see the affected versions and patch details below.
Silverstripe History XSS Vulnerability
Real-World Exposure
silverstripe/cmsReal-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
A cross-site scripting vulnerability has been discovered in the CMS page history tab.
This vulnerability can only be exploited if a user with CMS access has posted malicious or unescaped HTML into any of the text fields on a page, and if the "compare mode" option is selected. The HTML will be embedded into the page unescaped.
This has been resolved by performing the text comparison in a HTML friendly way.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/cms | ≥ 3.1.0&&< 3.1.10 | 3.1.10composer require silverstripe/cms:^3.1.10 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/cms to 3.1.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hh6-59j2-qrxw 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-6hh6-59j2-qrxw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-6hh6-59j2-qrxw. 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-6hh6-59j2-qrxw in your dependencies?
O3 Security finds GHSA-6hh6-59j2-qrxw across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.