Technology & security · · 9 min read · By Alexander
TYPO3 security vulnerability: What do you need to do now?
Find out whether your company website uses TYPO3 and which version is actually running. Then arrange the appropriate security update and configuration checks without delay. The reason is a critical TYPO3 security vulnerability among ten advisories published on 17 November 2026. Whether your site can be attacked also depends on access rights and settings. The ready-to-copy enquiry below will help you commission the checks.

What happened?
On 17 November 2026, TYPO3 published ten security advisories, TYPO3-CORE-SA-2026-025 to -034, along with the relevant updates. CVE-2026-119623 in the Install Tool is particularly important. TYPO3 rates it as “Critical”; the vendor’s official CVE record gives it a CVSS 4.0 severity score of 9.4. In combination with CVE-2026-119622 and under the conditions described below, it may allow third-party code to be executed on the server, technically known as RCE.
The updates affect branches 10 to 14. Other advisories cover form uploads, image processing and the page cache, among other areas. Have the complete security update for your branch installed. TYPO3 14 also requires the RSS configuration described below.
How serious is the installer vulnerability?
The documented attack chain can lead to third-party code being executed on the server. Initially, it requires a logged-in user with limited rights in the TYPO3 administration area (Backend), which is consistent with PR:L in the CVSS vector. Through CVE-2026-119622, this user can create an online media file in the publicly accessible main directory (Webroot), even without file permissions or module access. A suitable file whose name begins with FIRST_INSTALL then uses CVE-2026-119623 to reactivate the installer of an already configured, vulnerable website. Only this reactivated installer requires no login. It can be used to change the database connection and create Administrator or System Maintainer accounts with extensive privileges, potentially leading to RCE.
The marker file must exist in the Webroot or project directory, or it must be possible to create it there. It may also have been left behind or restored from a backup. If the marker is already present, the Backend login described above is not necessarily required. This does not demonstrate that any visitor can take over every installation without prerequisites.
In the sources reviewed, TYPO3 explicitly reports active exploitation of CVE-2026-125160. This form vulnerability can disclose upload paths. If, for example, HTML files are allowed and a restrictive Content Security Policy (CSP) is missing, third-party scripts can run in the browser, known as XSS. Here, the CSP is a browser security control. The sources give no victim numbers and do not demonstrate successful server takeovers. They do not confirm active exploitation of the installer chain.
Which TYPO3 version should you have installed?
Have the target version listed below for your branch installed and the required configuration checked. These fixes address the published vulnerabilities. ELTS is paid extended maintenance; publicly available release notes do not provide free access to the packages.
Free community support for TYPO3 12 ended on 30 April 2026. For ELTS, the team maintaining your site must confirm that it has access; the current fourth ELTS year for TYPO3 10 is reserved for TYPO3 partners. If maintenance has expired (EOL), you need available ELTS coverage or a planned move to a supported branch, including a compatibility check. For older versions not listed here, there is no evidence of either a fix or immunity.
The RSS issue CVE-2026-125165 affects only TYPO3 14.0.0 to 14.3.11. After the update, HTTP.allowed_hosts.dashboard_rss must define the permitted servers for news feeds in the Dashboard. If no such RSS widgets are used, the empty list [] must be entered explicitly. Leaving the value unset still allows requests to arbitrary hosts.
- TYPO3 10.4: 10.4.63 ELTS.
- TYPO3 11.5: 11.5.57 ELTS.
- TYPO3 12.4: 12.4.52 ELTS.
- TYPO3 13.4: 13.4.40 LTS, publicly available.
- TYPO3 14.3: 14.3.12 LTS, publicly available; an additional RSS host allowlist is required.
How should you check your website?
Start with the version shown at the top left of the Backend, if visible. Ask someone with sufficient file access to check the Webroot and project directory for every filename with the prefix FIRST_INSTALL. The team maintaining your site must confirm the actual location of both directories. They should also check for unknown Administrator and System Maintainer accounts. The absence of visible markers does not rule out a breach.
If you do not have the required access rights, pass these checks to the team maintaining your site. A hosting file manager may show only some of the directories. Plesk or cPanel does not prove that TYPO3 has been updated automatically. You can forward the following technical details directly:
- Forms: Have upload fields in the form editor and manually created form definitions checked. The permitted file types must be explicitly defined in allowedMimeTypes for every FileUpload and ImageUpload field. After the fix, an empty list blocks uploads.
- Upload protection: Have an effective, restrictive CSP confirmed for the actual upload directories. With Apache, the supplied fileadmin/.htaccess protects the default file storage; nginx requires manual configuration. The mere presence of the file does not prove effective protection. Any non-standard upload paths must also be checked.
- Page cache: Have FE.cacheHash.enforceValidation enabled. cHash validation must be enforced to prevent the described page-cache overload. Projects upgraded from older versions may differ from the defaults for new installations.
- Image processing: Have it checked whether uploads without MIME validation are subsequently processed with ImageMagick and an enabled MVG coder. This could expose local file contents readable by the web server through publicly accessible images. After the fix, special formats may require a mapping in SYS.FileInfo.fileExtensionToMimeType.
- Dashboard RSS: State whether user-configurable RSS widgets are used. For TYPO3 14, have the permitted feed hosts explicitly confirmed after the update.
What should you write to your hosting provider or agency?
Commission the update, including a backup and the configuration checks. Add your domain to this message:
Subject: Urgent TYPO3 check and security update for [Domain] Hello, please confirm whether our website uses TYPO3, which version is running in production and who is responsible for CMS maintenance. This request concerns TYPO3-CORE-SA-2026-025 to -034 dated 17 November 2026, particularly the installer chain CVE-2026-119623/CVE-2026-119622 and CVE-2026-125160, which the vendor reports as actively exploited. Please update the relevant branch to 10.4.63 ELTS, 11.5.57 ELTS, 12.4.52 ELTS, 13.4.40 LTS or 14.3.12 LTS. Where applicable, please confirm ELTS access and, before the update, a current, restorable backup of the website files and database. Check for FIRST_INSTALL* files in the Webroot and project root, as well as unknown Administrator/System Maintainer accounts. Check all form uploads for allowedMimeTypes and an effective upload CSP, including manual configuration for nginx. Confirm FE.cacheHash.enforceValidation, the ImageMagick/MVG conditions and, for TYPO3 14, HTTP.allowed_hosts.dashboard_rss with explicitly defined feed hosts or [] if no such widgets are used. Please provide the implementation date and then confirm the target version running in production and the completed configuration checks. Let us know about any anomalies and required follow-up steps. If there is a delay, we need an assessment of the remaining risks. Thank you [Name / Company]
What if the update cannot be installed immediately?
Ask the team maintaining your site to assess the remaining risks. The official partial measures do not replace the update: checking markers and accounts does not prevent files from being created again. A restrictive upload CSP limits the impact of XSS, but the path disclosure remains. Explicit MIME allowlists and enabling FE.cacheHash.enforceValidation are supplementary measures.
The security.form.allowUnrestrictedFileUploadMimeTypes switch restores the old, unsafe upload behaviour and is not a suitable safeguard. The advisory does not specify a replacement policy for ImageMagick. The new RSS allowlist is not a demonstrated interim fix for unpatched code. For several other vulnerabilities, the advisories reviewed document only the update as the solution.
If a prompt update and adequate safeguards are impossible, ask the team maintaining your site as a final step: “Does access to the affected application need to be temporarily restricted, or does it need to be taken offline until the issue is resolved?” The decision must be based on your website. The advisories do not recommend taking all affected sites offline.
More questions about the TYPO3 security vulnerability
Does this advisory also affect WordPress?
The vulnerabilities described affect TYPO3 components. A WordPress-only installation is not directly affected by them, but this is not a general assurance of security. Any additional TYPO3 installation must be checked separately.
Does Cloudflare protect against these vulnerabilities?
The underlying research does not demonstrate effective protection through Cloudflare. Arrange the TYPO3 updates and configuration checks.
Is a static website affected?
A purely static website without TYPO3 does not contain the vulnerable TYPO3 functions described here. Have it checked whether TYPO3 is also running in the same hosting account. This alone does not demonstrate that the static site is affected.
What can I check with editor access?
If enabled for your account, you can read the version display and view upload fields in the form editor. If you do not have sufficient rights, the team maintaining your site must carry out the full account checks and inspect the server files and effective server configuration.
Does “actively exploited” mean that my website has been hacked?
No. The vendor’s statement about CVE-2026-125160 does not demonstrate a breach of your website. The reviewed sources do not break down attempts, successful path disclosures and successful XSS. Your installation needs to be checked individually.
Is TYPO3 14.3.12 sufficient without any other changes?
No. For CVE-2026-125165, HTTP.allowed_hosts.dashboard_rss must also be configured: explicitly permit the required feed hosts or set [] if no such widgets are used. Leaving the list unset is not sufficient.