Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-125163

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

Overview

Published
17 Nov 2026
Modified
17 Nov 2026
Medium CVE
1 Registry packages
0 OS packages
0 Linux distributions
No Fix available
CVSS score Medium, no score

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.

Source: OX vulnerability database

Severity

MEDIUM

No CVSS vector in the source. Severity comes from the advisory.

Weakness: CWE-434

Affected packages · 1

Packages affected by CVE-2026-125163
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms-form >=11.0.0, <11.5.57>=10.0.0, <10.4.63>=14.0.0, <14.3.12>=13.0.0, <13.4.40>=12.0.0, <12.4.52 No fix yet

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.