CVE-2026-119623TYPO3 CMS Missing Authentication for Critical Function
NVD
Vulnerability Summary
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.
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.
CVSS v4.0 Base Metrics — Score 9.4 (CRITICAL)
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HAttack VectorNetwork
Attack ComplexityLow
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)High
Integrity (Subsequent System)High
Availability (Subsequent System)High
Affected & Patched Versions
- TYPO3 CMS >= 14.0.0 and < 14.3.12
- TYPO3 CMS >= 13.0.0 and < 13.4.40
- TYPO3 CMS >= 12.0.0 and < 12.4.52
- TYPO3 CMS >= 11.0.0 and < 11.5.57
- TYPO3 CMS >= 10.0.0 and < 10.4.63
- TYPO3 CMS 14.3.12
- TYPO3 CMS 13.4.40
- TYPO3 CMS 12.4.52
- TYPO3 CMS 11.5.57
- TYPO3 CMS 10.4.63
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is critical.
- Check whether you run TYPO3 CMS and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 17, 2026Published
- Nov 17, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new TYPO3 CMS CVEsYou are reading CVE-2026-119623. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsMore TYPO3 CMS CVEs
External References
- Vendor Advisoryhttps://news.typo3.com/security/advisory/typo3-core-sa-2026-027
- Patchhttps://github.com/TYPO3/typo3/commit/0f0a1ca5a5eae9349a38e6d34b096c01d9bf6d1d
- Patchhttps://github.com/TYPO3/typo3/commit/3ad2358f8208dc5258880ad4880c244123c5edf2
- Patchhttps://github.com/TYPO3/typo3/commit/1634e72112a69435759336cb363daac6d35956bc
Data last checked: Nov 17, 2026 12:31 UTC