CVE-2024-55893 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in typo3/cms-belog. A fix is available for typo3/cms-belog — see the affected versions and patch details below.
TYPO3 Cross-Site Request Forgery in Log Module
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2024-55893.
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-belog🐘typo3/cms-belog🐘typo3/cms-belog🐘typo3/cms-belogReal-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
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.enforceReferrerfeature is disabled,BE/cookieSameSiteconfiguration is set tolaxornone
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-belog | ≥ 10.0.0&&< 10.4.48 | 10.4.48composer require typo3/cms-belog:^10.4.48 |
| 🐘Packagist | typo3/cms-belog | ≥ 11.0.0&&< 11.5.42 | 11.5.42composer require typo3/cms-belog:^11.5.42 |
| 🐘Packagist | typo3/cms-belog | ≥ 12.0.0&&< 12.4.25 | 12.4.25composer require typo3/cms-belog:^12.4.25 |
| 🐘Packagist | typo3/cms-belog | ≥ 13.0.0&&< 13.4.3 | 13.4.3composer require typo3/cms-belog:^13.4.3 |
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-belog, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-belog to 10.4.48 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55893 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 CVE-2024-55893 in your dependencies?
Find it across Packagist, including transitive dependencies.