CVE-2026-125163
The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload.
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: low risk of data being read.
Affected products · TYPO3
| Product | Affected versions |
|---|---|
| TYPO3 CMS | from 14.0.0 before 14.3.12 from 13.0.0 before 13.4.40 from 12.0.0 before 12.4.52 from 11.0.0 before 11.5.57 from 10.0.0 before 10.4.63 |
Weakness classification
References
- NVD record
- CVE.org record
- https://news.typo3.com/security/advisory/typo3-core-sa-2026-032
- https://github.com/TYPO3/typo3/commit/c0b9519c254d58ad2a7bb4db354456c2b639e293
- https://github.com/TYPO3/typo3/commit/6adb8d66f3388e88a54fc6da6922b11d03379ee2
- https://github.com/TYPO3/typo3/commit/ed6fdc05939732e837e35063d02571051952c461