Visitors can upload any kind of file through some of your forms, including HTML and SVG files that browsers can run. Uploads go to a public folder by default. An attacker who learns a file's URL can use it for cross-site scripting (running their script in someone else's browser).
How it works
Form Framework upload fields use allowedMimeTypes as the list of file types they accept. The TYPO3 advisory says an empty list counted as "no restriction". That happens in hand-written form definitions, or when every type is deselected in the form editor. Only the file deny pattern then applied, and it only blocks PHP-related extensions. The fix makes an empty list refuse uploads.
Serving the upload folder with a restrictive Content-Security-Policy stops browsers from running such files. How attackers could learn a file's URL is covered by TYPO3-CORE-SA-2026-029.
After you update
An upload field with an empty allowedMimeTypes list now refuses every upload, so give each FileUpload and ImageUpload element at least one allowed type. The feature toggle security.form.allowUnrestrictedFileUploadMimeTypes brings back the old behavior, but TYPO3 advises against it.