TYPO3-CORE-SA-2026-032: Unrestricted File Upload in Form Framework

It has been discovered that TYPO3 CMS is susceptible to unrestricted file uploads in the Form Framework.
- Component Type: TYPO3 CMS
- Subcomponent: Form Framework (ext:form)
- Release Date: November 17, 2026
- Vulnerability Type: Unrestricted File Upload
- Affected Versions: 10.0.0-10.4.62, 11.0.0-11.5.56, 12.0.0-12.4.51, 13.0.0-13.4.39, 14.0.0-14.3.11
- Severity: Medium
- Suggested CVSS: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- References: CVE-2026-125163, CWE-434
Problem Description
The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. An empty allowedMimeTypes list was treated as "no restriction". Forms containing upload elements without any configured MIME type, for example in manually created form definitions or when all MIME types were deselected in the form editor, accepted any file except those blocked by the file deny pattern, which only covers PHP-related file extensions. This allowed unauthenticated users to upload files with browser-executable content, such as HTML or SVG documents, to the configured upload folder, which by default is located in a public storage. If attackers know the URL of an uploaded file (see TYPO3-CORE-SA-2026-029), this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder.
Solution
Update to TYPO3 versions 10.4.63 ELTS, 11.5.57 ELTS, 12.4.52 ELTS, 13.4.40 LTS or 14.3.12 LTS that fix the problem described.
Breaking Change Notice: An empty allowedMimeTypes list now refuses file uploads for the affected element. Integrators must configure at least one allowed MIME type for every FileUpload or ImageUpload element. The previous behavior can be restored temporarily with the feature toggle security.form.allowUnrestrictedFileUploadMimeTypes, which is not recommended. See ChangeLog entry #110695 for details.
Credits
Thanks to lichoin for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.
General Advice
Follow the recommendations that are given in the TYPO3 Security Guide.
General Note
All security-related code changes are tagged so you can easily look them up in our review system.