high CVSS 7.2

CVE-2025-47941·PHP vulnerability

TYPO3 is an open source, PHP based web content management system. In versions on the 12.x branch prior to 12.4.31 LTS and the 13.x branch prior to 13.4.2 LTS, 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. Users should update to TYPO3 version 12.4.31 LTS or 13.4.12 LTS to fix the problem.

Severity
high
Software
PHP
Fixed in
13.4.12
Published
2025-05-20

Affected versions

From: 13.0.0

Until: 13.4.12

Fixed in: 13.4.12

How to fix this CVE

TYPO3 versions 13.0.0 through 13.4.11 contain an MFA bypass vulnerability that allows authenticated backend users to circumvent multifactor authentication checks by exploiting insufficient route access restrictions. Immediately upgrade to TYPO3 13.4.12 LTS or apply the 12.4.31 LTS patch to re-enforce MFA validation across all backend entry points. This vulnerability requires valid backend credentials but poses a significant risk to administrative account security.

sudo dnf update php

Defensia detects this vulnerability

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement backend access control lists (ACLs) at the WAF level to ensure all administrative endpoints enforce MFA token validation before processing requests. Block backend requests lacking valid X-TYPO3-MFA-Token headers or session MFA-completion markers.

How to check if you are affected

  1. Check installed TYPO3 version: grep -r 'TYPO3_version' /var/www/html/typo3 or query SELECT version FROM typo3_be_sessions
  2. Verify vulnerable range: if installed version is between 13.0.0 and 13.4.11, the system is vulnerable
  3. Inspect TYPO3 backend logs at var/log/typo3_*.log for unauthorized backend access patterns or MFA bypass attempts
  4. Confirm remediation by verifying installed TYPO3 version is 13.4.12 or later: cat typo3/sysext/core/ext_emconf.php | grep version

FAQ

What is CVE-2025-47941?

CVE-2025-47941 is an authentication bypass vulnerability in TYPO3 CMS that allows authenticated backend administrators to skip multifactor authentication (MFA) verification by accessing backend routes without proper MFA checks, weakening the security posture of administrative sessions.

Is CVE-2025-47941 being actively exploited?

No, CVE-2025-47941 is not currently listed on the CISA Known Exploited Vulnerabilities catalog, and no public exploits are available. However, the vulnerability requires only valid backend credentials, making it a moderate threat in environments with compromised admin accounts.

What versions of TYPO3 are affected by CVE-2025-47941?

TYPO3 versions 13.0.0 through 13.4.11 are affected. The 12.x branch (prior to 12.4.31 LTS) is also vulnerable. Versions 13.4.12 LTS and 12.4.31 LTS contain the fix.

How do I check if my server is vulnerable to CVE-2025-47941?

Run: grep -i 'TYPO3' /var/www/html/typo3/sysext/core/ext_emconf.php | grep version to identify your TYPO3 release. If it falls between 13.0.0–13.4.11 or 12.0.0–12.4.30, your installation is vulnerable.

Does Defensia detect CVE-2025-47941?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP/TYPO3 is installed on a monitored server, CVE-2025-47941 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.
CVE-2025-46348CVSS 10YesWiki is a wiki system written in PHP. Prior to version 4.5.4, the request to commence a site backup can be performed and downloaded without authentication. The archives are created with a predictable filename, so a malicious user could create and download an archive without being authenticated. This could result in a malicious attacker making numerous requests to create archives and fill up the file system, or by downloading the archive which contains sensitive site information. This issue has been patched in version 4.5.4.
CVE-2025-47916CVSS 10Invision Community 5.0.0 before 5.0.7 allows remote code execution via crafted template strings to themeeditor.php. The issue lies within the themeeditor controller (file: /applications/core/modules/front/system/themeeditor.php), where a protected method named customCss can be invoked by unauthenticated users. This method passes the value of the content parameter to the Theme::makeProcessFunction() method; hence it is evaluated by the template engine. Accordingly, this can be exploited by unauthenticated attackers to inject and execute arbitrary PHP code by providing crafted template strings.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-47941. Free for 1 server.

Get started free