GHSA-fh99-4pgr-8j99
MEDIUMGHSA-fh99-4pgr-8j99 is a medium-severity (CVSS 5.3) CWE-532 vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-fh99-4pgr-8j99 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insertion of Sensitive Information into Log File in typo3/cms-core
Blast Radius
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:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C(4.9)
Problem
It has been discovered that system internal credentials or keys (e.g. database credentials) have been logged as plaintext in exception handlers, when logging the complete exception stack trace.
Solution
Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.
Credits
Thanks to Marco Huber who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 7.0.0&&< 7.6.57 | 7.6.57 |
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.47 | 8.7.47 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.35 | 9.5.35 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.29 | 10.4.29 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.11 | 11.5.11 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.29 | 10.4.29 |
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 7.6.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh99-4pgr-8j99 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-fh99-4pgr-8j99 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-fh99-4pgr-8j99. 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-fh99-4pgr-8j99 in your dependencies?
O3 detects GHSA-fh99-4pgr-8j99 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.