CVE-2025-47939
published 2025-05-20CVE-2025-47939: TYPO3 is an open source, PHP based web content management system. By design, the file management module in TYPO3’s backend user interface has historically…
PriorityP431medium5.4CVSS 3.1
AVNACLPRLUINSUCNILAL
EPSS
0.16%
5.4th percentile
TYPO3 is an open source, PHP based web content management system. By design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`) starting in version 9.0.0 and prior to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS. Although such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site. Users should update to TYPO3 version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.
Affected
16 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| msrc | cbl2_kernel_5.15.86.1-1_on_cbl_mariner_2.0 | — | — |
| typo3 | cms-core | >= 10.0.0 < 10.4.50 | 10.4.50 |
| typo3 | cms-core | >= 11.0.0 < 11.5.44 | 11.5.44 |
| typo3 | cms-core | >= 12.0.0 < 12.4.31 | 12.4.31 |
| typo3 | cms-core | >= 13.0.0 < 13.4.12 | 13.4.12 |
| typo3 | cms-core | >= 9.0.0 < 9.5.51 | 9.5.51 |
| typo3 | typo3 | — | — |
| typo3 | typo3 | — | — |
| typo3 | typo3 | — | — |
| typo3 | typo3 | — | — |
| typo3 | typo3 | — | — |
| typo3 | typo3 | >= 10.0.0 < 10.4.50 | 10.4.50 |
| typo3 | typo3 | >= 11.0.0 < 11.5.44 | 11.5.44 |
| typo3 | typo3 | >= 12.0.0 < 12.4.31 | 12.4.31 |
| typo3 | typo3 | >= 13.0.0 < 13.4.12 | 13.4.12 |
| typo3 | typo3 | >= 9.0.0 < 9.5.51 | 9.5.51 |
CVSS provenance
nvdv3.15.4MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
vendor_msrc9.8CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
osv·2025-05-20
CVE-2025-47939 [MEDIUM] TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
### Problem
By design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).
Although such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or
GHSA
TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
ghsa·2025-05-20
CVE-2025-47939 [MEDIUM] CWE-351 TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
### Problem
By design, the file management module in TYPO3’s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`).
Although such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or
Microsoft
An issue was discovered in ksmbd in the Linux kernel 5.15 through 5.19 before 5.19.2. fs/ksmbd/smb2pdu.c has a use-after-free and OOPS for SMB2_TREE_DISCONNECT.
vendor_msrc·2022-12-13·CVSS 9.8
CVE-2022-47939 [CRITICAL] CWE-416 An issue was discovered in ksmbd in the Linux kernel 5.15 through 5.19 before 5.19.2. fs/ksmbd/smb2pdu.c has a use-after-free and OOPS for SMB2_TREE_DISCONNECT.
An issue was discovered in ksmbd in the Linux kernel 5.15 through 5.19 before 5.19.2. fs/ksmbd/smb2pdu.c has a use-after-free and OOPS for SMB2_TREE_DISCONNECT.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-05-20
Published