# CVE-2025-47939: TYPO3 CMS Vulnerable to Unrestricted File Upload in File Abstraction Layer > Attackers can upload potentially harmful files to TYPO3, risking site availability or reputation via third-party security blocks. - **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 May 2025 - **Updated:** 20 May 2025 - **Also known as:** GHSA-9hq9-cr36-4wpj ## What is CVE-2025-47939? CVE-2025-47939 is a medium-severity vulnerability in Typo3 Typo3, published on 20 May 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-351 (Insufficient Type Distinction) ## Which versions are affected by CVE-2025-47939? 10 open source packages ship an affected version, including typo3/cms-core. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.50 | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.50 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.44 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.44 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.31 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.31 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.12 | | `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.12 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.51 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.51 | Products: Typo3 Typo3. ## How do I fix CVE-2025-47939? Upgrade typo3/cms-core to a fixed version for your release line: 10.4.50, 11.5.44, 12.4.31 or 13.4.12. ## Is CVE-2025-47939 being exploited? There is no known exploitation of CVE-2025-47939 in the wild and no public exploit code. ## Other vulnerabilities in Typo3 Typo3 - [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0) - [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8) - [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8) - [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8) - [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-47939 and fix it if it is affected. What it is: CVE-2025-47939 is a medium-severity vulnerability in Typo3 Typo3, published on 20 May 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-47939 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.50 - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.50 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.44 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.44 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.31 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.31 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.12 - typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.12 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.51 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.51 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-47939/ (Markdown: https://insights.sbomify.com/CVE-2025-47939/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47939 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47939 - OSV: https://osv.dev/vulnerability/CVE-2025-47939 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-47939/ Summaries are generated and may contain mistakes; the official description above is the record.