Skip to main content
CVE-2025-59018VulnerabilityPublished Updated

CVE-2025-59018: TYPO3 CMS · Information Exposure

Affects TYPO3 CMSSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
TYPO3 TYPO3 CMSAffected
  • =9.0.0
  • =10.0.0
  • =11.0.0
  • =12.0.0
  • =13.0.0
Fixed in–

AI-suggested

1. Immediate patching: Organizations should monitor TYPO3 CMS vendor announcements closely and apply security patches as soon as they become available. 2. Access control review: Restrict backend user privileges strictly to the minimum necessary. Audit user roles and permissions to ensure that only trusted users have backend access, especially to the Workspace Module. 3. Network segmentation: Limit backend access to trusted networks or VPNs to reduce exposure to unauthorized actors. 4. Monitoring and logging: Enable detailed logging of backend AJAX route accesses and monitor for unusual or unauthorized access patterns to detect exploitation attempts early. 5. Temporary disabling: If feasible, temporarily disable or restrict the Workspace Module’s AJAX backend routes until patches are applied. 6. Incident response preparedness: Prepare to respond to potential data leakage incidents by having data breach notification procedures and forensic capabilities in place. 7. User education: Train backend users on security best practices and the importance of safeguarding their credentials to prevent account compromise.

Description

Missing authorization checks in the Workspace Module of TYPO3 CMS versions 9.0.0‑9.5.54, 10.0.0‑10.4.53, 11.0.0‑11.5.47, 12.0.0‑12.4.36, and 13.0.0‑13.4.17 allow backend users to directly invoke the corresponding AJAX backend route to disclose sensitive information without having access.

References

Community reviews

Loading reviews…