CVE-2026-19418

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
12%
KEV
Not listed

Published

August 11, 2026

Last Modified

August 11, 2026

Advisory Details (5)

Auto-updated Aug 11, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 4a75e862c589 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit 4a75e862c589 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/4a75e862c589c85d795d7c65dcdc835f8f413efc
github_commit

commit a0e8ee06a40e (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit a0e8ee06a40e — awaiting tagged release

https://github.com/TYPO3/typo3/commit/a0e8ee06a40e959b9e7b06a4b1cb19d3a0d3dcf7
github_commit

commit ae0abd329d52 (TYPO3/typo3)

Fix landed in TYPO3/typo3 commit ae0abd329d52 — awaiting tagged release

https://github.com/TYPO3/typo3/commit/ae0abd329d52285fe6e92804c3608820ad45e872
generic

TYPO3-CORE-SA-2020-006: Same-Origin Request Forgery to Backend User Interface - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2020-006
generic

TYPO3-CORE-SA-2026-021: Broken Access Control in Backend and Install Tool - TYPO3 News

https://typo3.org/security/advisory/typo3-core-sa-2026-021

Vendor Advisories for CVE-2026-19418(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 03:42 UTCEG score recompute
  2. 2026-08-21 03:42 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 16:48 UTCGHSA enrichment
  5. 2026-08-20 05:36 UTCGHSA enrichment
  6. 2026-08-19 18:42 UTCEG score recompute
  7. 2026-08-19 18:42 UTCGHSA enrichment
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 07:41 UTCGHSA enrichment
  10. 2026-08-18 20:47 UTCEG score recompute
  11. 2026-08-18 20:47 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 09:54 UTCGHSA enrichment
  14. 2026-08-17 23:01 UTCEG score recompute
  15. 2026-08-17 23:00 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 12:07 UTCGHSA enrichment
  18. 2026-08-17 01:11 UTCEG score recompute
  19. 2026-08-17 01:11 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 14:17 UTCGHSA enrichment
  22. 2026-08-16 03:23 UTCEG score recompute
  23. 2026-08-16 03:23 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 16:30 UTCGHSA enrichment
Show 22 more
  1. 2026-08-15 05:36 UTCEG score recompute
  2. 2026-08-15 05:36 UTCGHSA enrichment
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 18:42 UTCGHSA enrichment
  5. 2026-08-14 07:49 UTCEG score recompute
  6. 2026-08-14 07:49 UTCGHSA enrichment
  7. 2026-08-13 22:00 UTCEPSS rescore
  8. 2026-08-13 20:55 UTCGHSA enrichment
  9. 2026-08-13 10:02 UTCGHSA enrichment
  10. 2026-08-12 23:08 UTCEG score recompute
  11. 2026-08-12 23:08 UTCGHSA enrichment
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-12 12:15 UTCGHSA enrichment
  14. 2026-08-12 01:17 UTCGHSA enrichment
  15. 2026-08-11 14:24 UTCEG score recompute
  16. 2026-08-11 14:24 UTCGHSA enrichment
  17. 2026-08-11 13:42 UTCEPSS rescore
  18. 2026-08-11 13:32 UTCEG score recompute
  19. 2026-08-11 13:32 UTCGHSA enrichment
  20. 2026-08-11 08:25 UTCEG score recompute
  21. 2026-08-11 07:33 UTCEG score recompute
  22. 2026-08-11 07:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19418?
CVE-2026-19418 is a high vulnerability published on August 11, 2026. 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…
When was CVE-2026-19418 disclosed?
CVE-2026-19418 was first published in the National Vulnerability Database on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19418 actively exploited?
CVE-2026-19418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.1% of all scored CVEs.
What is the CVSS score of CVE-2026-19418?
CVE-2026-19418 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-19418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19418, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-19418

Explore →

Is Your Infrastructure Affected by CVE-2026-19418?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs