TYPO3 CMS Stored Cross-Site Scripting via FileDumpControllerGHSA-9c6w-55cp-5w25
MEDIUMFix: TYPO3/typo3@5462084GHSA-9c6w-55cp-5w25 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9c6w-55cp-5w25.
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
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘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
Meta
- CVSS:
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C(5.0)
Problem
It has been discovered that the FileDumpController (backend and frontend context) is vulnerable to cross-site scripting when malicious files are displayed using this component. A valid backend user account is needed to exploit this vulnerability.
Solution
Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.
Credits
Thanks to Vautia who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.
References
- TYPO3-CORE-SA-2022-009
- Vulnerability Report on huntr.dev (embargoed +30 days)
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 7.0.0&&< 7.6.58 | 7.6.58composer require typo3/cms-core:^7.6.58 |
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.48 | 8.7.48composer require typo3/cms-core:^8.7.48 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.37 | 9.5.37composer require typo3/cms-core:^9.5.37 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.32 | 10.4.32composer require typo3/cms-core:^10.4.32 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.16 | 11.5.16composer require typo3/cms-core:^11.5.16 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.32 | 10.4.32composer require typo3/cms:^10.4.32 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 7.6.58 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9c6w-55cp-5w25 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-9c6w-55cp-5w25 in your dependencies?
Find it across Packagist, including transitive dependencies.