GHSA-jfp7-79g7-89rf
MEDIUMTYPO3 CMS vulnerable to Weak Authentication in Frontend Login
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
typo3/cms-core🐘typo3/cms-core🐘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
Problem
Restricting frontend login to specific users, organized in different storage folders (partitions), can be bypassed. A potential attacker might use this ambiguity in usernames to get access to a different account - however, credentials must be known to the adversary.
Solution
Update to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | all versions | 8.7.49 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.38 | 9.5.38 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.33 | 10.4.33 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.20 | 11.5.20 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.1.1 | 12.1.1 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.33 | 10.4.33 |
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 8.7.49 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfp7-79g7-89rf 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-jfp7-79g7-89rf 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-jfp7-79g7-89rf. 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-jfp7-79g7-89rf in your dependencies?
O3 detects GHSA-jfp7-79g7-89rf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.