Skip to content
TrustList
Security advisories

TYPO3 fixes ten flaws; one lets backend users seize the installer

Editorial

By TrustList Editorial

A form-upload leak in the same batch is already being exploited, one fix breaks upload fields left without a MIME list, and a dashboard flaw needs a setting as well as the update.

About TYPO3 fixes ten flaws; one lets backend users seize the installer

TYPO3 fixes ten flaws; one lets backend users seize the installer

17 November 2026: TYPO3 has released fixes for ten vulnerabilities in every supported branch of the content management system, led by CVE-2026-119623, a critical flaw that lets a low-privileged backend user re-open the first-install wizard and create a new administrator. A separate flaw in the Form Framework, CVE-2026-125160, is rated medium but is the one TYPO3 says is "known to be actively exploited".

Not yet independently verified. Severities and CVSS vectors are the TYPO3 security team's own suggested values, and its advisories give vectors without numeric scores. The statement that one flaw is actively exploited is TYPO3's; we have seen no independent account of the attacks. The release announcement for the new versions had not been posted when we read the advisories. We will update this when it can be confirmed, and remove this note.

Fixed versions for every branch

Nine of the ten advisories, TYPO3-CORE-SA-2026-025 to 033, affect all five maintained lines, and the tenth affects version 14 alone.

Branch Affected Fixed in
14 LTS 14.0.0 to 14.3.11 14.3.12
13 LTS 13.0.0 to 13.4.39 13.4.40
12 ELTS 12.0.0 to 12.4.51 12.4.52
11 ELTS 11.0.0 to 11.5.56 11.5.57
10 ELTS 10.0.0 to 10.4.62 10.4.63

The three older lines receive fixes only under the paid extended support programme, so a site on version 10, 11 or 12 without an ELTS contract has no patched release to move to.

Two flaws chain into a site takeover

The critical advisory, SA-2026-027, concerns the installer. A file whose name begins with FIRST_INSTALL, placed in the public web root or the project root, switched the first-install wizard back on without authentication. From there an attacker could change the database connection and create an administrator and system maintainer account, which leads to code execution.

SA-2026-026 (CVE-2026-119622, high) supplies the way to plant that file. The endpoint for adding online media such as video links accepted a target folder in the public web root with no permission check, so any logged-in backend user, even one with no file access at all, could create a file there with a partly controllable name. TYPO3 says the two together re-enable the installer on a configured site.

The update stores an explicit installing flag in the system configuration and accepts only the exact names FIRST_INSTALL and FIRST_INSTALL.txt. TYPO3 advises administrators to look in both root folders for unexpected FIRST_INSTALL files and to review the list of administrator and system maintainer accounts for entries nobody recognises.

The exploited leak and a breaking change to forms

SA-2026-029 is the flaw under attack. A failed upload through a public form showed the raw error message, including the storage path with its per-session folder name, which tells an attacker the public address of files they upload. SA-2026-032 (CVE-2026-125163) is its partner: an upload field with an empty list of allowed MIME types accepted anything except PHP-related files, HTML and SVG included.

The fix for the second changes behaviour. An upload element with an empty allowedMimeTypes list now refuses every upload, so integrators must set at least one MIME type on each upload field before or immediately after updating. A feature toggle restores the old behaviour, which TYPO3 does not recommend. Sites on nginx should also check that the upload folder is served with a restrictive Content-Security-Policy, which the shipped .htaccess does only for Apache.

Settings the update does not change for you

Three advisories need a decision from the administrator:

  • SA-2026-034 (version 14 only): the dashboard RSS widget could be made to request internal hosts. "Updating TYPO3 alone does not mitigate this vulnerability"; the allowed feed hosts must be listed in the HTTP allowed_hosts setting for dashboard_rss, or set to an empty list where the widget is unused.
  • SA-2026-031 (high): unauthenticated visitors could flood the page cache where cHash validation is not enforced. TYPO3 recommends switching on enforceValidation.
  • SA-2026-028 (high): an uploaded file could make ImageMagick read local files into a public image. After the update, formats such as PSD or PPM must be configured explicitly.

The remaining fixes cover a path traversal in the import module that gives code execution to users allowed to import (SA-2026-025, high), an open redirect in backend URL handling, and a token check in the file dump controller that let visitors fetch files from non-public storage.

Agencies that maintain TYPO3 sites for clients will find the form change the slowest part, since each upload field has to be checked by hand.

Related on TrustList:

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in