MODX vulnerability allows for XSS via user settings parametersGHSA-vwqw-wfhv-2xcq
MEDIUMFix: modxcms/revolution@c08fb7cGHSA-vwqw-wfhv-2xcq is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in modx/revolution. A fix is available for modx/revolution — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
modx/revolutionReal-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
MODX Revolution through v2.7.0-pl allows XSS via User Settings such as Description.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | modx/revolution | all versions | 2.7.1-plcomposer require modx/revolution:^2.7.1-pl |
Affected Products
modx revolutionmodxDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for modx/revolution, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update modx/revolution to 2.7.1-pl or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vwqw-wfhv-2xcq is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-vwqw-wfhv-2xcq in your dependencies?
Find it across Packagist, including transitive dependencies.