Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-19418

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

Overview

Published
11 Aug 2026
Modified
23 Oct 2026
High CVE
2 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available
CVSS score High, no score

Description

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.

Source: OX vulnerability database

Severity

HIGH

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-346, CWE-352

Affected packages · 2

Packages affected by CVE-2026-19418
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms-backend >=13.0.0, <13.4.34 13.4.34
Composer (PHP) typo3/cms-core >=14.0.0, <14.3.6>=13.0.0, <13.4.34 14.3.6

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.