External risk intelligence

TYPO3 Installer Re-enablement Leading to Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-119623

The vulnerability affects a web application (TYPO3) which is commonly deployed as a public-facing web platform. While the exploit requires specific file placement, the attack surface is an internet-reachable web application, and the installation wizard mechanism is a known component of such web-based content management systems.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A critical security vulnerability has been identified in the installation process of certain web applications, allowing unauthenticated access to reset system configurations and execute code remotely. This issue arises when a specific file is placed in the web root, re-enabling the setup wizard for already configured instances. The underlying technology allows for potential unauthorized control and code execution.

  • An attacker can reset system configurations.
  • It allows remote code execution without authentication.
  • Confirm relevance and exposure to the affected technology.

Attack Path

How an attacker could exploit the issue

An attacker could compromise an already set up instance by placing a specially named file in the web or project root, which would re-enable the installer. This would allow an unauthenticated attacker to alter database settings and create new administrative accounts, potentially leading to full system control and remote code execution. This could be achieved by an authenticated user with low privileges or through other means of placing files in the web root.

  • Requires placing a marker file.
  • Re-enables installer without authentication.
  • Leads to full system control.

Live Threat

Current exploitation, exposure, and threat context

On an already configured instance, an attacker could re-enable the installer by placing a specially named file in the web root. This would allow them to modify database connections and create new administrator accounts, potentially leading to remote code execution when supported by the advisory.

  • System configuration and access controls.
  • Placing a specially named file in the web root.
  • Unauthorized administrative control and code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability's impact on already configured TYPO3 instances necessitates collaboration between application owners and infrastructure or platform teams. The first practical step is to identify all deployed instances, confirm their reachability and business criticality, and locate the accountable owner for each. Remediation planning should then be prioritized based on these findings.

  • Application owners must own the issue.
  • Verify if the affected installer is enabled.
  • Plan remediation based on exposure.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is TYPO3 and what is the role of its installer?

TYPO3 is a widely used open-source content management system (CMS) designed for building and managing websites. Like many web platforms, it includes an installation wizard that automates the initial setup process, such as configuring database connections and creating the primary administrator account. Once the initial setup is complete, the installer is intended to be deactivated to secure the system against unauthorized configuration changes.

How does CVE-2026-119623 allow unauthorized access?

This vulnerability is classified as CWE-306, which refers to a missing authentication check. The weakness exists because the TYPO3 installer could be reactivated on an already configured site simply by placing a specific marker file in the web root. Once triggered, the installer ignores existing authentication requirements, allowing anyone to redefine system settings and create new accounts with administrative privileges, ultimately enabling remote code execution.

Does this bug trigger automatically without user action?

No. The vulnerability requires a specific precondition: a marker file starting with 'FIRST_INSTALL' must be placed within the web or project root directory. If no such file is present, the installer remains inactive. Simply visiting the site does not trigger the bug; the attacker must first successfully place this file, which could happen if they already have low-level access or if other server misconfigurations allow unauthorized file creation.

Is my TYPO3 instance at risk if it is internal only?

According to Halo Surface Signal, this vulnerability is categorized as having an external attack surface because TYPO3 is typically deployed as a public-facing platform. While internet-facing instances face the highest risk, internal instances could still be targeted by an attacker who has already breached your internal network or by a malicious user with low-level backend access who can drop the required marker file.

How should I respond to this security advisory?

Your first step is to perform an inventory of all your TYPO3 instances to determine where they are running and who is responsible for each one. Once identified, prioritize these systems based on their accessibility and business impact. Coordinate with your platform or infrastructure teams to update the software to a fixed version, which removes the ability to re-enable the installer via marker files and moves the installation state tracking into the secure system configuration.

References