The TYPO3 CMS Backend has Broken Authentication in Backend MFAGHSA-744g-7qm9-hjh9
HIGHFix: TYPO3-CMS/backend@034f589GHSA-744g-7qm9-hjh9 is a high-severity (CVSS 7.2) CWE-288 vulnerability in typo3/cms-backend. A fix is available for typo3/cms-backend — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-744g-7qm9-hjh9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
typo3/cms-backend🐘typo3/cms-backendReal-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
The multifactor authentication (MFA) dialog presented during backend login can be bypassed due to insufficient enforcement of access restrictions on all backend routes.
Successful exploitation requires valid backend user credentials, as MFA can only be bypassed after successful authentication.
Solution
Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
Credits
Thanks to Jens Jacobsen and Y. Kahveci for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-backend | ≥ 12.0.0&&< 12.4.31 | 12.4.31composer require typo3/cms-backend:^12.4.31 |
| 🐘Packagist | typo3/cms-backend | ≥ 13.0.0&&< 13.4.12 | 13.4.12composer require typo3/cms-backend:^13.4.12 |
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-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-backend to 12.4.31 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-744g-7qm9-hjh9 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.
Frequently Asked Questions
Is GHSA-744g-7qm9-hjh9 in your dependencies?
Find it across Packagist, including transitive dependencies.