GHSA-mgj2-q8wp-29rr
MEDIUMTYPO3 CMS vulnerable to Insufficient Session Expiration after Password Reset
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🐘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
When users reset their password using the corresponding password recovery functionality, existing sessions for that particular user account were not revoked. This applied to both frontend user sessions and backend user sessions.
Solution
Update to TYPO3 versions 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 | ≥ 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 |
| 🐘Packagist | typo3/cms | ≥ 11.0.0&&< 11.5.20 | 11.5.20 |
| 🐘Packagist | typo3/cms | ≥ 12.0.0&&< 12.1.1 | 12.1.1 |
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 10.4.33 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mgj2-q8wp-29rr 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-mgj2-q8wp-29rr 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-mgj2-q8wp-29rr. 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-mgj2-q8wp-29rr in your dependencies?
O3 detects GHSA-mgj2-q8wp-29rr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.