TYPO3 Allows Unrestricted File Upload in File Abstraction Layer

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

EPSS

• CVE-2025-47939: 0.18% estimated exploitation activity in the next 30 days; percentile 7.75 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 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. Solution Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS,…

Published by the source

20 May 2025, 19:35 UTC

Last modified by the source

21 May 2025, 04:39 UTC

Source last checked

26 Oct 2026, 14:33 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9hq9-cr36-4wpj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-47939

Advisory: TYPO3 Allows Unrestricted File Upload in File Abstraction Layer
IDs: CVE-2025-47939, GHSA-9hq9-cr36-4wpj
Record: https://patchnext.com/advisories/cve-2025-47939 (revision 1, source checked 26 Oct 2026, 14:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 13.4.12, 12.4.31, 11.5.44, 10.4.50, 9.5.51. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 9.0.0, <= 9.5.50; >= 10.0.0, <= 10.4.49; >= 11.0.0, <= 11.5.43; >= 12.0.0, <= 12.4.30; >= 13.0.0, <= 13.4.11; fixed in 13.4.12, 9.5.51, 10.4.50, 11.5.44, 12.4.31

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9hq9-cr36-4wpj (GitHub-reviewed advisory GHSA-9hq9-cr36-4wpj lists affected ranges: Packagist typo3/cms-core >=9.0.0 =10.0.0 =11.0.0 =12.0.0 =13.0.0 <=13.4.11)

Commands are suggestions: review each one before running it.