CVE-2026-119623 · TYPO3 / TYPO3 CMS
CVE-2026-119623
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
TYPO3 / TYPO3 CMS · semver
CVE vendor record- affected: From 14.0.0 (inclusive) · before 14.3.12 (exclusive) · semver
- affected: From 13.0.0 (inclusive) · before 13.4.40 (exclusive) · semver
- affected: From 12.0.0 (inclusive) · before 12.4.52 (exclusive) · semver
- affected: From 11.0.0 (inclusive) · before 11.5.57 (exclusive) · semver
- affected: From 10.0.0 (inclusive) · before 10.4.63 (exclusive) · semver
Fixed releases / commits: Not explicitly provided by this source. Check the vendor guidance.
Repository: https://github.com/TYPO3/typo3
Other versions: unaffected according to the vendor record.
Advisory overview
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.
