CVE-2026-119623: TYPO3 CMS · Missing Authentication for Critical Functionality
Affects TYPO3 CMSSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical · fixed in 14.3.12 : patch TYPO3 CMS as a priority.
Data as of 17 Nov 2026, 11:34 UTC
Thin evidence
One scorer or none| CNA (TYPO3) | CVSS 4.0 | 9.4 |
|---|
- Patch
- Available – fixed in 14.3.12, 13.4.40, 12.4.52 +2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3 CMStypo3/cms-install | Affected
| Fixed in
|
| TYPO3 CMStypo3/cms-install | Affected
| Fixed in
|
| TYPO3 CMStypo3/cms-install | Affected
| Fixed in
|
| TYPO3 CMStypo3/cms-install | Affected
| Fixed in
|
| TYPO3 CMStypo3/cms-install | Affected
| Fixed in
|
Packagisttypo3/cms-installpkg:composer/typo3/cms-installOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official TYPO3 CMS updates to versions 14.3.12, 13.4.40, 12.4.52, 11.5.57, or 10.4.63 or later, which fix this vulnerability by preventing installer re-enablement via marker files and restricting accepted marker filenames. No additional mitigation is required once these patches are applied.
Description
CVE-2026-119623 is a critical vulnerability in TYPO3 CMS where the installer wizard can be re-enabled on an already configured instance by placing a specially named file in the web root. This allows unauthenticated access to the installer, enabling attackers to modify the database connection and create privileged accounts, potentially leading to remote code execution. The flaw can be exploited by low-privileged authenticated users or through leftover marker files. Fixed versions prevent re-enabling the installer via marker files and restrict accepted marker filenames.