Open Redirection in Login HandlingGHSA-4jhw-2p6j-5wmp
MEDIUMGHSA-4jhw-2p6j-5wmp is a medium-severity (CVSS 6.1) Open Redirect vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-4jhw-2p6j-5wmp by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms+1 moreReal-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
It has been discovered that Login Handling is susceptible to open redirection which allows attackers redirecting to arbitrary content, and conducting phishing attacks. No authentication is required in order to exploit this vulnerability.
Solution
Update to TYPO3 versions 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
Credits
Thanks to Alexander Kellner who reported this issue and to TYPO3 security team member Torben Hansen who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 6.2.0&&< 6.2.57 | 6.2.57composer require typo3/cms-core:^6.2.57 |
| 🐘Packagist | typo3/cms-core | ≥ 7.0.0&&< 7.6.51 | 7.6.51composer require typo3/cms-core:^7.6.51 |
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.40 | 8.7.40composer require typo3/cms-core:^8.7.40 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.14 | 10.4.14composer require typo3/cms-core:^10.4.14 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.1.1 | 11.1.1composer require typo3/cms-core:^11.1.1 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.25 | 9.5.25composer require typo3/cms-core:^9.5.25 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 6.2.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4jhw-2p6j-5wmp is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is GHSA-4jhw-2p6j-5wmp in your dependencies?
Find it across Packagist, including transitive dependencies.