CVE-2024-55893: TYPO3 Cross-Site Request Forgery in Log Module
Problem A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method.
Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions:
the user opens a malicious link, such as one sent via email. the user visits a compromised or manipulated website while the following settings are misconfigured: + security.backend.enforceReferrer feature is disabled, + BE/cookieSameSite configuration is set to lax or none
The vulnerability in the affected downstream component “Log Module” allows attackers to remove log entries.
Solution Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.
Credits Thanks to Gabriel Dimitrov who reported this issue and to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.
References TYPO3-CORE-SA-2025-003
Other sources
TYPO3 Cross-Site Request Forgery in Log Module
— Packagist
TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. security.backend.enforceReferrer feature is disabled, 2. BE/cookieSameSite configuration is set to lax or none. The vulnerability in the affected downstream component “Log Module” allows attackers to remove log entries. Users are advised to update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS which fix the problem described. There are no known workarounds for this vulnerability.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/typo3/cms-belogto a version that resolves this vulnerability.Fixed in 13.4.3 - Upgrade
Upgrade
composer/typo3/cms-belogto a version that resolves this vulnerability.Fixed in 12.4.25 - Upgrade
Upgrade
composer/typo3/cms-belogto a version that resolves this vulnerability.Fixed in 11.5.42 - Upgrade
Upgrade
composer/typo3/cms-belogto a version that resolves this vulnerability.Fixed in 10.4.48 - Upgrade
Upgrade
TYPO3to a version that resolves this vulnerability.Fixed in 11.5.42 ELTSPatch TYPO3-CORE-SA-2025-003
Event History
Frequently Asked Questions
What applications are affected by CVE-2024-55893?
CVE-2024-55893 affects TYPO3 CMS versions 10.0.0 to 10.4.47, 11.0.0 to 11.5.41, 12.0.0 to 12.4.24, and 13.0.0 to 13.4.2.
What is the severity of CVE-2024-55893?
CVE-2024-55893 is classified as a medium severity vulnerability due to its potential exploitation through Cross-Site Request Forgery.
How do I fix CVE-2024-55893?
To fix CVE-2024-55893, upgrade TYPO3 CMS to versions 13.4.3, 12.4.25, 11.5.42, or 10.4.48.
What type of vulnerability is CVE-2024-55893?
CVE-2024-55893 is a Cross-Site Request Forgery (CSRF) vulnerability that affects the backend user interface functionality.
What impact does CVE-2024-55893 have on TYPO3 CMS?
CVE-2024-55893 allows attackers to perform state-changing actions without proper authorization on the affected TYPO3 CMS systems.