CVE-2026-119623
Last modified
CVE-2026-119623 is a critical-severity vulnerability rated 9.4/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| TYPO3 | 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 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-119623?
How severe is CVE-2026-119623?
How do I fix CVE-2026-119623?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-119618Concurrent Execution using Shared Resource with Improper Syn…8.1
- CVE-2026-119619A vulnerability was found in 37954679 cak-filemanagement-sys…7.3
- CVE-2026-11962The FileOrganizer WordPress plugin before 1.2.0 does not va…8.8
- CVE-2026-119620A vulnerability was determined in 37954679 cak-filemanagemen…7.3
- CVE-2026-119621When importing a T3D or XML file in the Import/Export module…7.7
- CVE-2026-119622The backend endpoint for adding online media (e.g. YouTube o…7.1
- CVE-2026-119625The `/{username}` web route accepted personal access tokens …4.3
- CVE-2026-119627The web profile and RSS/Atom feed routes of users and organi…4.3
- CVE-2026-11963The User Registration & Membership WordPress plugin before …8.1
- CVE-2026-119634The User Frontend – Membership, User Registration, User Prof…6.3
- CVE-2026-119635The Groundhogg plugin for WordPress is vulnerable to Stored …7.2
- CVE-2026-119636Improper release of expired privileged access checkouts in t…8.8
Are you affected by CVE-2026-119623?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
