TYPO3 · TYPO3 CMS · CWE-306 · published 2026-11-17
CVE-2026-119623TYPO3 CMS - Missing Authentication in Installer
Routine No exploitation evidence; EPSS 0.7%.
CVE-2026-119623 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 53% of all CVEs. This TYPO3 CMS vulnerability: CVSS 9.4 (v4.0), a successful attack gives total control of the component. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.7% (53th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.4 (v4.0)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-306: Missing Authentication for Critical Functionality
Affected versions (from the CVE record)#
- TYPO3 TYPO3 CMS
14.0.0to before14.3.12(affected)13.0.0to before13.4.40(affected)12.0.0to before12.4.52(affected)11.0.0to before11.5.57(affected)10.0.0to before10.4.63(affected)
Description (from the CVE record)#
The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way. With the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['isInstalling'] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files.
Quoted from the CVE Program record.