Skip to content

The TYPO3 CMS Backend has Broken Authentication in Backend MFA

High severity GitHub Reviewed Published May 20, 2025 in TYPO3/typo3

Package

composer typo3/cms-backend (Composer)

Affected versions

>= 12.0.0, <= 12.4.30
>= 13.0.0, <= 13.4.11

Patched versions

12.4.31
13.4.12

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.

References

@ohader ohader published to TYPO3/typo3 May 20, 2025
Published by the National Vulnerability Database May 20, 2025
Published to the GitHub Advisory Database May 20, 2025
Reviewed May 20, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(24th percentile)

Weaknesses

CVE ID

CVE-2025-47941

GHSA ID

GHSA-744g-7qm9-hjh9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.