CVE-2026-15305 json
TYPO3 CMS - Unrestricted File Upload in Form Framework
published 3mo ago modified 16d ago also GHSA-mfqj-cqv3-h7xw , EUVD-2026-43671
- cvss
- 6.3
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
Users were able to upload files with arbitrary MIME types to forms using FileUpload or ImageUpload elements with allowedMimeTypes configured. The restriction was not enforced server-side because the MimeTypeValidator was registered during form building before concrete form definition properties were applied, resulting in the validator never being added to the processing pipeline. This issue affects TYPO3 CMS versions 14.2.0-14.3.4.
Patch / fix
- packagist typo3/cms-form 14.3.5
- TYPO3 TYPO3 CMS 14.3.5
- github.com/TYPO3/typo3@817ad41 commit
- github.com/TYPO3/typo3@cfda210 commit
Is CVE-2026-15305 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3mo ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | typo3/cms-form | >=14.2.0, <14.3.5 |
14.3.5 |
Affected products
- TYPO3 TYPO3 CMS
Classification
- Weakness
-
- CWE-351 Insufficient Type Distinction
References
-
github.com
/TYPO3/typo3/commit/817ad41cc9dd28aac0fc4d0fe16fc25d46dd554a
patch, web
-
github.com
/TYPO3/typo3/commit/cfda21050398eb145211a4fa6f9988f10e43e10b
patch, web
-
typo3.org
/security/advisory/typo3-core-sa-2026-020
vendor-advisory, web
-
github.com
/TYPO3/typo3/security/advisories/GHSA-mfqj-cqv3-h7xw
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-15305
advisory
-
github.com
/FriendsOfPHP/security-advisories/blob/master/typo3/cms-form/CVE-2026-15305.yaml
web
-
github.com
/TYPO3/typo3
package
-
news.typo3.com
/security/advisory/typo3-core-sa-2026-020
web
Sources
- CVE List CVE-2026-15305
- GitHub Advisory GHSA-mfqj-cqv3-h7xw
- NVD CVE-2026-15305
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.