Skip to main content
Menu
CVEs

CVE

TYPO3 CMS Install unauthenticated installer access enables code execution

Affects TYPO3 CMS 10.0.0 through 14.3.11 when an instance is configured and a file whose name starts with FIRST_INSTALL is in the public web root or project root. Fixed in 10.4.63, 11.5.57, 12.4.52, 13.4.40 and 14.3.12.

CVE-2026-119623EUVD-2026-126975

Written by a model from the sources below. Verify against them.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affected TYPO3 CMS versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11. The instance is already configured, and a file whose name starts with FIRST_INSTALL is present in the public web root or the project root.

Published
Last modified
Reference
Last checked
28/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

TYPO3 CMS could let an attacker re-enable its first-installation wizard on a configured site by placing a file whose name starts with FIRST_INSTALL in the web root or project root. An attacker with a low-privileged backend login can reach the installer remotely without authentication, change the database connection, and create administrator accounts, which can lead to remote code execution.

Original 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.

Who should check

Teams running TYPO3 CMS 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39 or 14.0.0-14.3.11, including TYPO3 installs from Packagist.

“Affected Versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11”

news.typo3.com

cve.now Index

28Pcve.now Index 28 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure8/25Specific setups only, reachable over the network
  • Reach10/20Affects Packagist packages
  • Severity10/10CVSS 9.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 35 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Affected TYPO3 CMS versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11. The instance is already configured, and a file whose name starts with FIRST_INSTALL is present in the public web root or the project root.
  • Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119623 (TYPO3 CMS - Missing Authentication in Installer), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119623 (entry last updated 2026-11-17):
Affected:
- Packagist package typo3/cms-install: from 14.0.0, fixed in 14.3.12; from 13.0.0, fixed in 13.4.40; from 12.0.0, fixed in 12.4.52; from 11.0.0, fixed in 11.5.57; from 10.0.0, fixed in 10.4.63
Fixed versions: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63.
Conditions (all must be true for the bug to be hit):
- Affected TYPO3 CMS versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-027)
- The instance is already configured, and a file whose name starts with FIRST_INSTALL is present in the public web root or the project root. (source: https://news.typo3.com/security/advisory/typo3-core-sa-2026-027)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-119623 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119623 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-027
- https://github.com/TYPO3/typo3/commit/0f0a1ca5a5eae9349a38e6d34b096c01d9bf6d1d
- https://github.com/TYPO3/typo3/commit/3ad2358f8208dc5258880ad4880c244123c5edf2
- https://github.com/TYPO3/typo3/commit/1634e72112a69435759336cb363daac6d35956bc
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119623
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119623"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Posted on X by cve.now
  5. Record last updated

Affected versions

  • From 14.0.0 · fixed in 14.3.12; From 13.0.0 · fixed in 13.4.40; From 12.0.0 · fixed in 12.4.52; From 11.0.0 · fixed in 11.5.57; From 10.0.0 · fixed in 10.4.63

Evidence 6

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 3

  1. Patch
  2. Patch
  3. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119623

Is CVE-2026-119623 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The installer can be reached without logging in. An anonymous visitor could change the database connection and create a new administrator and system maintainer account, which the advisory says leads to remote code execution.Source: news.typo3.com

Which versions are affected by CVE-2026-119623?

typo3/cms-install (Packagist): from 14.0.0 before 14.3.12; from 13.0.0 before 13.4.40; from 12.0.0 before 12.4.52; from 11.0.0 before 11.5.57; from 10.0.0 before 10.4.63.Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are TYPO3 CMS 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39 and 14.0.0-14.3.11. The advisory requires an already configured instance with a file whose name starts with FIRST_INSTALL in the public web root or project root, so check the installed TYPO3 version and look for such a file in those directories.Source: news.typo3.com

How do I fix CVE-2026-119623?

Upgrade to a fixed version: 14.3.12, 13.4.40, 12.4.52, 11.5.57, 10.4.63. The vendor's advisory also recommends 10.4.63 ELTS or 11.5.57 ELTS or 12.4.52 ELTS or 13.4.40 LTS or 14.3.12 LTS or later.Source: cve.now feed data, news.typo3.com

Why do the sources disagree?

The description says the installer is accessible without authentication, but the CVSS vector records privileges required as low (PR:L). The sources do not reconcile these two statements.Source: news.typo3.com

More CVEs