TYPO3 Cross-Site Request Forgery in Log Module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2024-55893: 0.25% estimated exploitation activity in the next 30 days; percentile 16.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

14 Jan 2025, 15:24 UTC

Last modified by the source

2 Jun 2025, 07:46 UTC

Source last checked

26 Oct 2026, 14:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cjfr-9f5r-3q93

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-55893

Advisory: TYPO3 Cross-Site Request Forgery in Log Module
IDs: CVE-2024-55893, GHSA-cjfr-9f5r-3q93
Record: https://patchnext.com/advisories/cve-2024-55893 (revision 1, source checked 26 Oct 2026, 14:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-belog 13.4.3, 12.4.25, 11.5.42, 10.4.48. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-belog: affected >= 10.0.0, <= 10.4.47; >= 11.0.0, <= 11.5.41; >= 12.0.0, <= 12.4.24; >= 13.0.0, <= 13.4.2; fixed in 10.4.48, 13.4.3, 11.5.42, 12.4.25

## Suggested inspection (read-only)
- Packagist typo3/cms-belog: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-belog.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cjfr-9f5r-3q93 (GitHub-reviewed advisory GHSA-cjfr-9f5r-3q93 lists affected ranges: Packagist typo3/cms-belog >=10.0.0 =11.0.0 =12.0.0 =13.0.0 <=13.4.2)

Commands are suggestions: review each one before running it.