TYPO3 CMS up to 11.5.50/12.4.45/13.4.30/14.3.2 Media path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.63- |
Summary
A vulnerability identified as critical has been detected in TYPO3 CMS up to 11.5.50/12.4.45/13.4.30/14.3.2. The impacted element is an unknown function of the component Media Module. The manipulation leads to path traversal. This vulnerability is uniquely identified as CVE-2026-49742. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in TYPO3 CMS up to 11.5.50/12.4.45/13.4.30/14.3.2. This issue affects some unknown functionality of the component Media Module. The manipulation with an unknown input leads to a path traversal vulnerability. Using CWE to declare the problem leads to CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Impacted is confidentiality. The summary by CVE is:
Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose sensitive files such as log files. This issue affects TYPO3 CMS versions 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.
The advisory is shared at typo3.org. The identification of this vulnerability is CVE-2026-49742 since 06/01/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 11.5.51, 12.4.46, 13.4.31 or 14.3.3 eliminates this vulnerability. Applying the patch ad636b6183843b57c758a1e12174a75093ac93c3 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). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- TYPO3 Core
Product
Type
Vendor
Name
Version
- 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: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Path traversalCWE: CWE-22
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 11.5.51/12.4.46/13.4.31/14.3.3
Patch: ad636b6183843b57c758a1e12174a75093ac93c3
Timeline
06/01/2026 CVE reserved06/09/2026 Advisory disclosed
06/09/2026 VulDB entry created
06/10/2026 VulDB entry last update
Sources
Advisory: typo3.orgStatus: Confirmed
CVE: CVE-2026-49742 (🔒)
GCVE (CVE): GCVE-0-2026-49742
GCVE (VulDB): GCVE-100-369497
CERT Bund: WID-SEC-2026-1835 - TYPO3 Core: Mehrere Schwachstellen
Entry
Created: 06/09/2026 13:33Updated: 06/10/2026 05:32
Changes: 06/09/2026 13:33 (70), 06/10/2026 05:32 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.