GHSA-cg75-qfg2-w9hj
GHSA-cg75-qfg2-w9hj is a Cross-site Scripting (XSS) vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-cg75-qfg2-w9hj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
TYPO3 CMS has Cross-Site Scripting in Indexed Search
Blast Radius
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-indexed-search🐘typo3/cms-indexed-searchReal-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
Problem
Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding, resulting in a Cross-Site Scripting vulnerability.
Solution
Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described.
Credits
TYPO3 CMS thanks Jan Kahmen and Sanjay Singh Jhala for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.
Resources
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 13.0.0&&< 13.4.31 | 13.4.31 |
| 🐘Packagist | typo3/cms-core | ≥ 14.0.0&&< 14.3.3 | 14.3.3 |
| 🐘Packagist | typo3/cms-indexed-search | ≥ 13.0.0&&< 13.4.31 | 13.4.31 |
| 🐘Packagist | typo3/cms-indexed-search | ≥ 14.0.0&&< 14.3.3 | 14.3.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/cms-core to 13.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cg75-qfg2-w9hj 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 pinpoints whether GHSA-cg75-qfg2-w9hj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-cg75-qfg2-w9hj. 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-cg75-qfg2-w9hj in your dependencies?
O3 detects GHSA-cg75-qfg2-w9hj across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.