CVE-2026-14982
HighCVSS 8.1Exploitation Probability (EPSS)
Low risk42th percentile - higher than 42% of all known CVEs
Summary
The WP File Download plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete function in all versions. Authenticated attackers with subscriber-level access and above can delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The two-stage exploit requires a first request to the file.save task to persist the path-traversal string into file metadata, followed by a second request to the file.delete task to trigger the unlink call — both endpoints lack capability checks and nonce enforcement.
Risk Assessment
An attacker can delete critical files such as wp-config.php, potentially leading to full compromise of the WordPress installation.
Recommendation
Update the WP File Download plugin to the latest patched version and restrict user permissions to the minimum.
Other vulnerabilities in WP File Download
See all- CVE-2026-94538High
The WP File Download plugin for WordPress is vulnerable to authorization bypass in all versions up to and including 6.3.9. The plugin does not properly verify that a user is authorized to perform an action.
- CVE-2026-14975Medium
The WP File Download plugin for WordPress is vulnerable to Directory Traversal in all versions up to and including 6.3.8 via the 'remoteurl' parameter. This allows authenticated attackers with subscriber-level access and above to read the contents of arbitrary files on the server, which can contain sensitive information. An authenticated attacker first poisons the _wpfd_file_metadata['file'] post-meta value via the unprotected file.save handler, after which the streaming endpoint, hooked on init with no authentication requirement, resolves and streams the traversed file path to any caller, including unauthenticated visitors.
Original NVD description (English source)
The WP File Download plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete function in all versions. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). The two-stage exploit requires a first request to the file.save task to persist the path-traversal string into file metadata, followed by a second request to the file.delete task to trigger the unlink call — both endpoints lack capability checks and nonce enforcement.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS