CVE-2026-19418: TYPO3 CMS · Origin Validation Error
Affects TYPO3 CMSSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.3 High : upgrade to 14.3.6 or 13.4.34 soon.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 14.3.6, 13.4.34
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 11 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 8 Nov 2026.
What to do
Upgrade TYPO3 CMS and typo3/cms-backend and typo3/cms-core to 14.3.6 or 13.4.34; TYPO3 CMS and typo3/cms-install to 14.3.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
Packagisttypo3/cms-backendpkg:composer/typo3/cms-backendOther threats | Affected
| Fixed in
|
Packagisttypo3/cms-corepkg:composer/typo3/cms-coreOther threats | Affected
| Fixed in
|
Packagisttypo3/cms-installpkg:composer/typo3/cms-installOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, restrict or remediate any cross-site scripting vulnerabilities that could enable attacker-controlled JavaScript execution on the TYPO3 domain, as this is a prerequisite for exploitation.
Description
### Problem The referrer enforcement introduced with [TYPO3-CORE-SA-2020-006](https://news.typo3.com/security/advisory/typo3-core-sa-2020-006) ([CVE-2020-11069](https://www.cve.org/CVERecord?id=CVE-2020-11069)) became ineffective in TYPO3 v13.0, where TYPO3 CMS started serving the backend and Admin Tool applications from the site's main entry script instead of the dedicated typo3/ directory. Whether a request originated from the backend or Install Tool itself was determined by comparing the referrer against the directory of the entry script, which since then is the site root. As a consequence, requests originating from any script running on one of the TYPO3 instance's own domains, such as a frontend page, were accepted by backend routes and Install Tool endpoints. Attackers able to execute JavaScript on one of those domains, for instance by exploiting a cross-site scripting vulnerability, could invoke these endpoints via Fetch/XHR with the privileges of an authenticated victim's user session. ### Solution Update to TYPO3 versions 13.4.34 LTS, 14.3.6 LTS that fix the problem described. ### Credits Thanks to Hổ Cao Từ for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.
References
- typo3.org/security/advisory/typo3-core-sa-2026-021 (opens in a new tab)
- typo3.org/security/advisory/typo3-core-sa-2020-006 (opens in a new tab)
- github.com/TYPO3/typo3/commit/ae0abd329d52285fe6e92804c3608820ad45e872 (opens in a new tab)
- github.com/TYPO3/typo3/commit/a0e8ee06a40e959b9e7b06a4b1cb19d3a0d3dcf7 (opens in a new tab)
- github.com/TYPO3/typo3/commit/4a75e862c589c85d795d7c65dcdc835f8f413efc (opens in a new tab)