| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in TYPO3 CMS up to 10.4.56/11.5.50/12.4.45/13.4.30/14.3.2. This impacts an unknown function. This manipulation causes case sensitivity. The identification of this vulnerability is CVE-2026-47346. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability has been found in TYPO3 CMS up to 10.4.56/11.5.50/12.4.45/13.4.30/14.3.2 and classified as critical. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a case sensitivity vulnerability. The CWE definition for the vulnerability is CWE-178. The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Backend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., .FORM.YAML) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
It is possible to read the advisory at typo3.org. This vulnerability is known as CVE-2026-47346 since 05/19/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 10.4.57, 11.5.51, 12.4.46, 13.4.31 or 14.3.3 eliminates this vulnerability. Applying the patch 2030617e6f273cee7b756c695f0a48a45a31eb47 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-1835). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Affected
- TYPO3 Core
Product
Type
Vendor
Name
Version
- 10.4.0
- 10.4.1
- 10.4.2
- 10.4.3
- 10.4.4
- 10.4.5
- 10.4.6
- 10.4.7
- 10.4.8
- 10.4.9
- 10.4.10
- 10.4.11
- 10.4.12
- 10.4.13
- 10.4.14
- 10.4.15
- 10.4.16
- 10.4.17
- 10.4.18
- 10.4.19
- 10.4.20
- 10.4.21
- 10.4.22
- 10.4.23
- 10.4.24
- 10.4.25
- 10.4.26
- 10.4.27
- 10.4.28
- 10.4.29
- 10.4.30
- 10.4.31
- 10.4.32
- 10.4.33
- 10.4.34
- 10.4.35
- 10.4.36
- 10.4.37
- 10.4.38
- 10.4.39
- 10.4.40
- 10.4.41
- 10.4.42
- 10.4.43
- 10.4.44
- 10.4.45
- 10.4.46
- 10.4.47
- 10.4.48
- 10.4.49
- 10.4.50
- 10.4.51
- 10.4.52
- 10.4.53
- 10.4.54
- 10.4.55
- 10.4.56
- 11.5.0
- 11.5.1
- 11.5.2
- 11.5.3
- 11.5.4
- 11.5.5
- 11.5.6
- 11.5.7
- 11.5.8
- 11.5.9
- 11.5.10
- 11.5.11
- 11.5.12
- 11.5.13
- 11.5.14
- 11.5.15
- 11.5.16
- 11.5.17
- 11.5.18
- 11.5.19
- 11.5.20
- 11.5.21
- 11.5.22
- 11.5.23
- 11.5.24
- 11.5.25
- 11.5.26
- 11.5.27
- 11.5.28
- 11.5.29
- 11.5.30
- 11.5.31
- 11.5.32
- 11.5.33
- 11.5.34
- 11.5.35
- 11.5.36
- 11.5.37
- 11.5.38
- 11.5.39
- 11.5.40
- 11.5.41
- 11.5.42
- 11.5.43
- 11.5.44
- 11.5.45
- 11.5.46
- 11.5.47
- 11.5.48
- 11.5.49
- 11.5.50
- 12.4.0
- 12.4.1
- 12.4.2
- 12.4.3
- 12.4.4
- 12.4.5
- 12.4.6
- 12.4.7
- 12.4.8
- 12.4.9
- 12.4.10
- 12.4.11
- 12.4.12
- 12.4.13
- 12.4.14
- 12.4.15
- 12.4.16
- 12.4.17
- 12.4.18
- 12.4.19
- 12.4.20
- 12.4.21
- 12.4.22
- 12.4.23
- 12.4.24
- 12.4.25
- 12.4.26
- 12.4.27
- 12.4.28
- 12.4.29
- 12.4.30
- 12.4.31
- 12.4.32
- 12.4.33
- 12.4.34
- 12.4.35
- 12.4.36
- 12.4.37
- 12.4.38
- 12.4.39
- 12.4.40
- 12.4.41
- 12.4.42
- 12.4.43
- 12.4.44
- 12.4.45
- 13.4.0
- 13.4.1
- 13.4.2
- 13.4.3
- 13.4.4
- 13.4.5
- 13.4.6
- 13.4.7
- 13.4.8
- 13.4.9
- 13.4.10
- 13.4.11
- 13.4.12
- 13.4.13
- 13.4.14
- 13.4.15
- 13.4.16
- 13.4.17
- 13.4.18
- 13.4.19
- 13.4.20
- 13.4.21
- 13.4.22
- 13.4.23
- 13.4.24
- 13.4.25
- 13.4.26
- 13.4.27
- 13.4.28
- 13.4.29
- 13.4.30
- 14.3.0
- 14.3.1
- 14.3.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Case sensitivityCWE: CWE-178 / CWE-697
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: CMS 10.4.57/11.5.51/12.4.46/13.4.31/14.3.3
Patch: 2030617e6f273cee7b756c695f0a48a45a31eb47
Timeline
05/19/2026 CVE reserved06/09/2026 Advisory disclosed
06/09/2026 VulDB entry created
06/09/2026 VulDB entry last update
Sources
Advisory: typo3.orgStatus: Confirmed
CVE: CVE-2026-47346 (🔒)
GCVE (CVE): GCVE-0-2026-47346
GCVE (VulDB): GCVE-100-369499
CERT Bund: WID-SEC-2026-1835 - TYPO3 Core: Mehrere Schwachstellen
Entry
Created: 06/09/2026 13:33Updated: 06/09/2026 15:11
Changes: 06/09/2026 13:33 (69), 06/09/2026 15:11 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.