TYPO3 core security releases of 2026-11-17 (ten advisories): a low-privileged backend user can write a file into the web root and re-enable the unauthenticated installer, which creates an administrator and leads to code execution (SA-026, SA-027 Critical), and TYPO3 states that a Form Framework flaw (SA-029) is actively exploited; fixed in 14.3.12, 13.4.40, 12.4.52 ELTS, 11.5.57 ELTS and 10.4.63 ELTS
TYPO3: backend user to installer to admin and RCE (SA-027 Critical); Form Framework flaw SA-029 exploited; update now
Defender actions
- Update every TYPO3 instance to 14.3.12, 13.4.40, 12.4.52 ELTS, 11.5.57 ELTS or 10.4.63 ELTS now, and on 14.x configure HTTP/allowed_hosts/dashboard_rss; until then check the public web root and the project root for unexpected files whose name starts with FIRST_INSTALL and the backend for administrator or system maintainer accounts nobody created, because a low-privileged backend user can re-enable the installer and TYPO3 states that one flaw in the same release is actively exploited.
Analysis
TYPO3 released ten core advisories on 2026-11-17, fixed in 14.3.12 LTS, 13.4.40 LTS, 12.4.52 ELTS, 11.5.57 ELTS and 10.4.63 ELTS (TYPO3, 2026-11-17); versions 10.0.0 to 10.4.62, 11.0.0 to 11.5.56, 12.0.0 to 12.4.51, 13.0.0 to 13.4.39 and 14.0.0 to 14.3.11 are affected (TYPO3 SA-027, 2026-11-17). SA-027 is rated Critical: placing a file whose name starts with FIRST_INSTALL in the public web root or the project root re-enables the installer on a configured instance without authentication, which allows changing the database connection and creating a new administrator and system maintainer account, and that leads to remote code execution; leftover or restored marker files also work (TYPO3 SA-027, 2026-11-17). SA-026, rated High, supplies the file: the backend endpoint for adding online media accepts a target folder in the fallback storage, which points to the public web root, so any authenticated low-privileged backend user can create media files with a partially controllable name there (TYPO3 SA-026, 2026-11-17).
TYPO3 states that SA-029, a Medium information disclosure in the Form Framework, is known to be actively exploited, and names no actor, victim or behaviour (TYPO3 SA-029, 2026-11-17). A failed upload shows the raw storage error with the upload sub-folder, so an attacker can derive the public URL of an uploaded file, and where the form accepts HTML this becomes cross-site scripting unless the web server applies TYPO3's recommended Content-Security-Policy to the upload folder (TYPO3 SA-029, 2026-11-17). SA-032 closes the matching gap, an empty allowedMimeTypes list that was treated as no restriction and let unauthenticated visitors upload HTML or SVG to a public folder (TYPO3 SA-032, 2026-11-17). SA-028 lets ImageMagick's MVG coder disclose any web-server-readable file through a processed image; it needs ImageMagick with its default configuration allowing the MVG coder, and unauthenticated visitors reach it where such an upload form exists (TYPO3 SA-028, 2026-11-17). SA-025 is an Import/Export path traversal that writes arbitrary files and needs an administrator or a user enabled for import (TYPO3 SA-025, 2026-11-17). Four lesser flaws are an incomplete open-redirect fix (SA-030), page-cache flooding where cHash validation is not enforced (SA-031), file-dump token reuse (SA-033) and an SSRF in the 14.x Dashboard RSS widget (SA-034) (TYPO3 SA-030, 2026-11-17; SA-031; SA-033; SA-034).
Cited evidence
This vulnerability is known to be actively exploited.
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
any authenticated, low-privileged backend user, even without file mounts or module access, could create online media files with a partially controllable file name in the public web root.
Sources11
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.