TYPO3
- Missing Authentication in Installer
Not on CISA's list of exploited flaws, and not in the news we track.
CVE-2026-119623Critical9.4
Chance of exploitation in the next 30 days
0.94%
EPSS score from FIRST
Black Shard's team can check your exposure to CVE-2026-119623 and take the fix off your plate.
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.
Updated 19 Nov 2026, 13:25 UTC, 32 of 36 sources answering.
Black Shard's team can check your exposure, take a fix off your plate or step in on a live incident.