Advisory record · GHSA-cjfr-9f5r-3q93

TYPO3 Cross-Site Request Forgery in Log Module

CVSS 4.3 MediumEPSS 0.0025 · 16th percentile

Published by the GitHub Advisory Database at 14 Jan 2025, 15:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-belogPackagist>=10.0.0, <10.4.48 || >=11.0.0, <11.5.42 || >=12.0.0, <12.4.25 || >=13.0.0, <13.4.310.4.48, 11.5.42, 12.4.25, 13.4.3
Identifiers
GHSA-cjfr-9f5r-3q93 · CVE-2024-55893 · PKSA-vz6p-3jbg-f6db
Weakness (CWE)
CWE-352 · CWE-749
Published
14 Jan 2025
Updated
20 May 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

TYPO3's belog package (the Log Module) is vulnerable to cross-site request forgery in versions from 10.0.0 up to 10.4.48, 11.0.0 up to 11.5.42, 12.0.0 up to 12.4.25, and 13.0.0 up to 13.4.3. An attacker can trick a logged-in backend user, via a malicious link or a compromised website under certain settings, into removing log entries. Upgrade to 10.4.48, 11.5.42, 12.4.25, or 13.4.3, as applicable.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0025, the 16th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:27 UTC First seen by agentprime
  2. 31 Oct 2026, 14:27 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.