Skip to main navigation Skip to main content Skip to page footer

TYPO3-CORE-SA-2026-027: Missing Authentication in Installer

It has been discovered that TYPO3 CMS is susceptible to missing authentication in the installer.



Problem Description

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.

Solution

Update to TYPO3 versions 10.4.63 ELTS, 11.5.57 ELTS, 12.4.52 ELTS, 13.4.40 LTS or 14.3.12 LTS that fix the problem described.

Administrators are advised to check the public web root and the project root for unexpected files whose name starts with FIRST_INSTALL, and to review backend user accounts with administrator or system maintainer privileges for unknown entries.

Credits

Thanks to 0xkidz for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.

General Advice

Follow the recommendations that are given in the TYPO3 Security Guide.

General Note

All security-related code changes are tagged so you can easily look them up in our review system.