TYPO3 CMS - Information Disclosure in Form Framework (CVE-2026-125160)
Published Last modified Sources: BSI, TYPO3, CVE.org, EUVD
- Actively exploited
- Source: VulnCheck KEV (opens in a new tab) How we classify
What is affected, what to do
Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory.
The vulnerability is being actively exploited; treat it as a priority. Update TYPO3 CMS to version 14.3.12, TYPO3 CMS to version 13.4.40, TYPO3 CMS to version 12.4.52.
- Affected
- TYPO3 CMS
lt 14.0.0..14.3.12 - TYPO3 CMS
lt 13.0.0..13.4.40 - TYPO3 CMS
lt 12.0.0..12.4.52 - TYPO3 CMS
lt 11.0.0..11.5.57 - TYPO3 CMS
lt 10.0.0..10.4.63
- TYPO3 CMS
- Fixed in
- TYPO3 CMS
14.3.12 - TYPO3 CMS
13.4.40 - TYPO3 CMS
12.4.52 - TYPO3 CMS
11.5.57 - TYPO3 CMS
10.4.63
- TYPO3 CMS
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
6.3
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v4
6.3
CVSS v4
Severity Medium on the scale from 0 to 10.
Source: BSI, TYPO3, CVE.org, EUVD
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- Medium
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 61.50 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 6.3 Methodology
CVSS v4
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 6.3
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 17 November 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-209
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form. If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.
Source: BSI CSAF, BSI WID Portal, typo3_advisory, cvelistv5, ENISA EUVD, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| TYPO3 | TYPO3 CMS |
|
|
| TYPO3 | Extension LTS |
|
|
Vendors and products
Weakness classes (CWE)
CWE-209Generation of Error Message Containing Sensitive Information
Base
The product generates an error message that includes sensitive information about its environment, users, or associated data.
Entry at MITRE CWE-209
References & sources
- news.typo3.comsecurity/advisory/typo3-core-sa-2026-029Vendor advisory, euvd
- github.comGit commit of 13.4 brancheuvd, Patch
- github.comGit commit of 14.3 brancheuvd, Patch
- github.comGit commit of main brancheuvd, Patch
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedTYPO3
Show 3 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/TYPO3/typo3/commit/9a6ee621672ab2b5cdf49dd9f32ff83dc69b941eReference added —https://github.com/TYPO3/typo3/commit/a85657b507e3f4c6fb62a94c1a41ad13441af655Reference added —https://github.com/TYPO3/typo3/commit/aecfd9afaffdb9c924df7b62ef39aacd26a34c3cSource identifier: f4fb688c-4412-4426-b4b8-421ecf27b14a
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-125160","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-17T11:30:05.544966Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedTYPO3
CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:A
Weakness type: CWE-209
Description added or changed
Show 5 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form. If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.CVSS added —AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:A/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XWeakness type (CWE) added —CWE-209Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/125xxx/CVE-2026-125160.json">CVE-2026-125160</a>Reference added —https://news.typo3.com/security/advisory/typo3-core-sa-2026-029Source identifier: f4fb688c-4412-4426-b4b8-421ecf27b14a
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-125160"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-125160.svg?lang=en" alt="CVE-2026-125160 – NEOSEC Intel" height="20"></a>