TYPO3CMS
CVE-2025-47939
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTYPO3 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTYPO3's backend file management module lacks proper file type restrictions, allowing upload of potentially harmful files (e.g., .exe binaries) and files with mismatched extensions/MIME types (e.g., file named .png but containing application/zip content). While these files aren't directly web-executable, they can trigger third-party security scanners to flag or block the site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TYPO3CMS
>= 9.0.0, < 9.5.51>= 10.0.0, < 10.4.50>= 11.0.0, < 11.5.44>= 12.0.0, < 12.4.31>= 13.0.0, < 13.4.12CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed TYPO3 versionCheck the TYPO3 version by reviewing the Composer.json file in the project root, or by accessing the TYPO3 Install Tool (typo3/install.php) and viewing the About section, or by checking typo3/sysext/core/Classes/Information/Typo3Version.phpAffected if The installed version falls within any of these ranges: 9.0.0 to <9.5.51, 10.0.0 to <10.4.50, 11.0.0 to <11.5.44, 12.0.0 to <12.4.31, or 13.0.0 to <13.4.12
-
Confirm backend file module is accessibleVerify that the TYPO3 backend file management module (Filelist) is enabled and accessible to backend users. Check user group permissions in the TYPO3 Access module to see if users have access to the File>List module.Affected if The Filelist module is enabled and backend users can access it to perform file uploads
-
Review file upload restrictions configurationInspect the TYPO3 configuration file (LocalConfiguration.php or AdditionalConfiguration.php) for the fileDenyPattern setting under $GLOBALS['TYPO3_CONF_VARS']['BE']. Also check for any custom file type validation rules in the file module configuration.Affected if The fileDenyPattern is missing, insufficiently restrictive, or allows upload of executable file types (.exe, .bat, .cmd, .msi, .com, .pif) and files with MIME type mismatches are not validated on upload
A user is affected if their TYPO3 installation version is within the affected ranges AND the backend file management module is accessible without proper file type validation enforcing both extension and MIME type consistency.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.5.5110.4.5011.5.44
Update TYPO3 to version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to receive the file type restriction fix.
TYPO3 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, or 12.4.31 LTS (depending on current branch)
- 1. Create a complete backup of the TYPO3 installation including database and all files
- 2. Identify the currently installed TYPO3 version branch (9.x, 10.x, 11.x, or 12.x)
- 3. For TYPO3 9.x: Upgrade to version 9.5.51 ELTS
- 4. For TYPO3 10.x: Upgrade to version 10.4.50 ELTS
- 5. For TYPO3 11.x: Upgrade to version 11.5.44 ELTS
- 6. For TYPO3 12.x: Upgrade to version 12.4.31 LTS
- 7. After upgrading, clear all TYPO3 caches via Install Tool or command line (typo3cms cache:flush)
- 8. Verify the file upload functionality works correctly and test the new file restriction behavior
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47939 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47939 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data