GHSA-954j-f27r-cj52
HIGHGHSA-954j-f27r-cj52 is a high-severity (CVSS 8.1) CWE-312 vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-954j-f27r-cj52 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cleartext storage of session identifier
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘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
User session identifiers were stored in cleartext - without processing of additional cryptographic hashing algorithms. This vulnerability cannot be exploited directly and occurs in combination with a chained attack - like for instance SQL injection in any other component of the system.
Solution
Update to TYPO3 versions 9.5.23 or 10.4.10 that fix the problem described.
Credits
Thanks to TYPO3 security team member Helmut Hummel who reported this issue and to TYPO3 core & security team members Benni Mack & Oliver Hader as well as TYPO3 contributor Markus Klein who fixed the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.23 | 9.5.23 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.10 | 10.4.10 |
| 🐘Packagist | typo3/cms-core | ≥ 8.7.0&&< 8.7.38 | 8.7.38 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.10 | 10.4.10 |
| 🐘Packagist | typo3/cms | ≥ 9.0.0&&< 9.5.23 | 9.5.23 |
| 🐘Packagist | typo3/cms | ≥ 8.7.0&&< 8.7.38 | 8.7.38 |
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 9.5.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-954j-f27r-cj52 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-954j-f27r-cj52 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-954j-f27r-cj52. 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-954j-f27r-cj52 in your dependencies?
O3 detects GHSA-954j-f27r-cj52 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.