CVE-2026-19418
HIGHDescription
The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 (CVE-2020-11069) became ineffective in TYPO3 v13.0, where TYPO3 CMS started serving the backend and Install 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. This issue affects TYPO3 CMS versions 13.0.0-13.4.33 and 14.0.0-14.3.5.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/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:X
Exploit Intelligence
Low risk: more likely to be exploited than 11% of all known CVEs.
References
Related Vulnerabilities
Other CWE-346 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-34291 | High | 8.8 | 84% | KEV | - |
| CVE-2009-1185 | High | 7.2 | 82% | - | Fix |
| CVE-2015-4495 | High | 8.8 | 71% | KEV | Fix |
| CVE-2020-16952 | High | 8.6 | 71% | - | - |
| CVE-2023-29711 | Critical | 9.8 | 70% | - | - |
| CVE-2024-23898 | High | 8.8 | 67% | - | Fix |
Common questions
How do I fix CVE-2026-19418?
No published fix for CVE-2026-19418 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-19418 being actively exploited?
Not that we know of. CVE-2026-19418 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.21% is the estimated probability that it will be exploited in the next 30 days. That is higher than 11% of all scored CVEs.
How severe is CVE-2026-19418?
CVE-2026-19418 has a CVSS v4 base score of 7.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-19418
Markdown
[](https://tridentstack.com/cve/CVE-2026-19418)HTML
<a href="https://tridentstack.com/cve/CVE-2026-19418"><img src="https://tridentstack.com/cve/badge/CVE-2026-19418.svg" alt="CVE-2026-19418"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-26.