What is CVE-2024-55893?

CVE-2024-55893 is a medium-severity cross-site request forgery (CSRF) vulnerability in typo3/cms-belog (composer), affecting versions >= 10.0.0, <= 10.4.47. It is fixed in 10.4.48, 11.5.42, 12.4.25, 13.4.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.

How severe is CVE-2024-55893?

CVE-2024-55893 has a CVSS score of 4.3 (Medium). 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-belog are affected by CVE-2024-55893?

typo3/cms-belog (composer) versions >= 10.0.0, <= 10.4.47 is affected.

Is there a fix for CVE-2024-55893?

Yes. CVE-2024-55893 is fixed in 10.4.48, 11.5.42, 12.4.25, 13.4.3. Upgrade to this version or later.

Is CVE-2024-55893 exploitable, and should I be worried?

Whether CVE-2024-55893 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.

What actually determines whether CVE-2024-55893 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-2024-55893?

Upgrade: typo3/cms-belog to 10.4.48 or later, typo3/cms-belog to 11.5.42 or later, typo3/cms-belog to 12.4.25 or later, typo3/cms-belog to 13.4.3 or later.

CVE-2024-55893 in typo3/cms-belog

Q: How severe is CVE-2024-55893?

CVE-2024-55893 has a CVSS score of 4.3 (Medium). 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.

Q: Which versions of typo3/cms-belog are affected by CVE-2024-55893?

typo3/cms-belog (composer) versions >= 10.0.0, <= 10.4.47 is affected.

Q: Is there a fix for CVE-2024-55893?

Yes. CVE-2024-55893 is fixed in 10.4.48, 11.5.42, 12.4.25, 13.4.3. Upgrade to this version or later.

Q: Is CVE-2024-55893 exploitable, and should I be worried?

Whether CVE-2024-55893 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.

Q: What actually determines whether CVE-2024-55893 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.

Q: How do I fix CVE-2024-55893?

Upgrade: typo3/cms-belog to 10.4.48 or later, typo3/cms-belog to 11.5.42 or later, typo3/cms-belog to 12.4.25 or later, typo3/cms-belog to 13.4.3 or later.

Summary

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.

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

Impact

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2024-55893 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. 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 (10.4.48, 11.5.42, 12.4.25, 13.4.3); upgrading removes the vulnerable code path.

Affected versions

typo3/cms-belog (>= 10.0.0, <= 10.4.47) typo3/cms-belog (>= 11.0.0, <= 11.5.41) typo3/cms-belog (>= 12.0.0, <= 12.4.24) typo3/cms-belog (>= 13.0.0, <= 13.4.2)

Security releases

typo3/cms-belog → 10.4.48 (composer) typo3/cms-belog → 11.5.42 (composer) typo3/cms-belog → 12.4.25 (composer) typo3/cms-belog → 13.4.3 (composer)

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 environment New to Kodem? Get a demo →

Remediation advice

Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.

Frequently Asked Questions

What is CVE-2024-55893? CVE-2024-55893 is a medium-severity cross-site request forgery (CSRF) vulnerability in typo3/cms-belog (composer), affecting versions >= 10.0.0, <= 10.4.47. It is fixed in 10.4.48, 11.5.42, 12.4.25, 13.4.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
How severe is CVE-2024-55893? CVE-2024-55893 has a CVSS score of 4.3 (Medium). 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-belog are affected by CVE-2024-55893? typo3/cms-belog (composer) versions >= 10.0.0, <= 10.4.47 is affected.
Is there a fix for CVE-2024-55893? Yes. CVE-2024-55893 is fixed in 10.4.48, 11.5.42, 12.4.25, 13.4.3. Upgrade to this version or later.
Is CVE-2024-55893 exploitable, and should I be worried? Whether CVE-2024-55893 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-2024-55893 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-2024-55893?
- Upgrade typo3/cms-belog to 10.4.48 or later
- Upgrade typo3/cms-belog to 11.5.42 or later
- Upgrade typo3/cms-belog to 12.4.25 or later
- Upgrade typo3/cms-belog to 13.4.3 or later