Summary
The TYPO3 CMS Backend has Broken Authentication in Backend MFA
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.
Credits
Thanks to Jens Jacobsen and Y. Kahveci for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.
Impact
CVE-2025-47941 has a CVSS score of 7.2 (High). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.4.31, 13.4.12); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
Frequently Asked Questions
- What is CVE-2025-47941? CVE-2025-47941 is a high-severity security vulnerability in typo3/cms-backend (composer), affecting versions >= 12.0.0, <= 12.4.30. It is fixed in 12.4.31, 13.4.12.
- How severe is CVE-2025-47941? CVE-2025-47941 has a CVSS score of 7.2 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of typo3/cms-backend are affected by CVE-2025-47941? typo3/cms-backend (composer) versions >= 12.0.0, <= 12.4.30 is affected.
- Is there a fix for CVE-2025-47941? Yes. CVE-2025-47941 is fixed in 12.4.31, 13.4.12. Upgrade to this version or later.
- Is CVE-2025-47941 exploitable, and should I be worried? Whether CVE-2025-47941 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-47941 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-47941?
- Upgrade
typo3/cms-backendto 12.4.31 or later - Upgrade
typo3/cms-backendto 13.4.12 or later
- Upgrade