WordPress: Unrestricted Upload of File with Dangerous Type
CVE-2026-65640 is a high-severity unrestricted upload of file with dangerous type vulnerability in WordPress, with a CVSS 3.0 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 7.0.4 as the first without the flaw, so updating WordPress to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.94% chance of exploitation within 30 days, higher than 80% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update WordPress to 7.0.4 or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (hackerone.com).
Official description
WordPress is vulnerable to a remote code execution vulnerability via malicious Postscript file upload by an Author level user or higher. Prerequisites: * Imagick and Ghostscript in use on the server * A malicious user with the `upload_files` capability This issue affects all versions of WordPress. Version 7.0.4 has been released, containing a fix for the vulnerability, and as a courtesy to users on older branches the fix has been backported to all branches back to 4.7.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Unrestricted Upload of File with Dangerous Type
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
How developers prevent this class of flaw
- Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
- Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
More Unrestricted Upload of File with Dangerous Type vulnerabilities (CWE-434)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
Other vulnerabilities in WordPress
- 8.1 High severity
- 8.1 High severity
WordPress Core Remote File Inclusion Exploited
- 8.9 High severity
- 9.8 Critical severity
WordPress Core Interpretation Conflict Exploited
- 5.9 Medium severity
WordPress Core SQL Injection Exploited
- 9.8 Critical severity
Recent Unrestricted Upload of File with Dangerous Type vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.7 High severity
- 8.8 High severity
- 8.8 High severity
Spotted an error? Tell us.