TYPO3 CMS - Unrestricted File Upload in Form Framework
Affected packages
| Package | Affected → Fixed | |
|---|---|---|
| TYPO3TYPO3 CMS |
≥ 14.0.0, < 14.3.12→ 14.3.12 ≥ 13.0.0, < 13.4.40→ 13.4.40 ≥ 12.0.0, < 12.4.52→ 12.4.52 ≥ 11.0.0, < 11.5.57→ 11.5.57 ≥ 10.0.0, < 10.4.63→ 10.4.63 |
14.3.12 13.4.40 12.4.52 11.5.57 10.4.63 |
Original description The description as published by the source.
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.
Source: CVE.org (CVE Program・cvelistV5) NVD
References
- advisory news.typo3.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- patch github.com
- web packagist.org