Cross-Site Scripting in TYPO3 BackendGHSA-5wx6-xwxf-q8qj
MEDIUMGHSA-5wx6-xwxf-q8qj is a medium-severity (CVSS 4.6) vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.
Real-World Exposure
typo3/cms🐘typo3/cms🐘typo3/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
Failing to properly encode user input, some backend components are vulnerable to Cross-Site Scripting. A valid backend user account is needed to exploit this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms | ≥ 6.2.0&&< 6.2.20 | 6.2.20composer require typo3/cms:^6.2.20 |
| 🐘Packagist | typo3/cms | ≥ 7.6.0&&< 7.6.5 | 7.6.5composer require typo3/cms:^7.6.5 |
| 🐘Packagist | typo3/cms | ≥ 8.0.0&&< 8.0.1 | 8.0.1composer require typo3/cms:^8.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 6.2.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5wx6-xwxf-q8qj 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-5wx6-xwxf-q8qj in your dependencies?
Find it across Packagist, including transitive dependencies.