CVE-2026-119623
TYPO3 CMS missing installer authentication allows code execution (CVE-2026-119623)
TYPO3 CMS can have its first-installation wizard re-enabled by a FIRST_INSTALL marker file. On configured sites the installer becomes accessible without authentication, allowing database changes, new admin and system-maintainer accounts, and remote code execution. Upgrade to the fixed builds.
What happened
TYPO3 CMS uses a first-installation wizard that should be unavailable after a site is configured. A missing-authentication flaw allows that installer to be re-enabled on an already configured instance if a file whose name begins with FIRST_INSTALL is written to the public web root or the project root. Once re-enabled, the installer can be reached without authentication.
An attacker who can place such a file can then change the database connection and create a new administrator and system maintainer account, which leads to remote code execution. The file can be created by an authenticated, low-privileged backend user without any further permissions, as demonstrated in TYPO3-CORE-SA-2026-026, or it can arise from leftover or restored marker files. The CVSS 4.0 score is 9.4 (critical). No active exploitation is reported in the CVE record.
Who is affected
Configured TYPO3 CMS instances on these branches are affected: 14.0.0 to before 14.3.12, 13.0.0 to before 13.4.40, 12.0.0 to before 12.4.52, 11.0.0 to before 11.5.57, and 10.0.0 to before 10.4.63. TYPO3 CMS is commonly an internet-facing content management system, and the affected condition is an already configured site where the installer was thought to be disabled.
What to do now
- Upgrade each affected site to the fixed release for its branch: TYPO3 CMS 14.3.12, 13.4.40, 12.4.52, 11.5.57, or 10.4.63.
- Check the public web root and project root for files with names beginning FIRST_INSTALL and remove any unexpected marker files on configured sites.
- If you cannot patch immediately, restrict network access to the install tool where possible and remove marker files to stop the installer from being re-enabled.
- Audit TYPO3 backend users for new administrator or system maintainer accounts you did not create, and review the database connection settings if there is any sign the installer was accessed.
How to detect it
On configured installations, check the public web root and project root for unexpected files whose names begin FIRST_INSTALL; these are the trigger for the flaw. Review TYPO3 backend user lists for administrator or system maintainer accounts that your team did not create, and watch web server access logs for requests to the installation area after initial setup.
Beyond the patch
TYPO3 CMS often powers public websites, so this flaw can turn a low-privileged backend account or a stray marker file into full site takeover. After patching, test for this class of missing-authentication and configuration issue, and have monitoring ready for the account creation and code execution that follows exploitation. Implementation & Assessment Services can test for and harden these authentication paths, while Managed Detection & Response can detect the post-compromise activity the attack leaves behind.
Affected and fixed versions
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3 CMS | 14.0.0 – < 14.3.12 13.0.0 – < 13.4.40 12.0.0 – < 12.4.52 11.0.0 – < 11.5.57 10.0.0 – < 10.4.63 | 14.3.12 13.4.40 12.4.52 11.5.57 10.4.63 11.5.57, 12.4.52, 13.4.40, 14.3.12 |