WordPress security changelog
HIGH CVE-2026-14982 Deferred

WP File Download permits Subscriber-level arbitrary file deletion

WP File Download through 6.3.4 exposes file.save and file.delete without capability or nonce enforcement. A Subscriber or higher can first persist a path-traversal value in file metadata through file.save, then invoke file.delete so the delete function passes that value to unlink(), deleting an arbitrary server file. Deleting a critical file such as wp-config.php can lead to site compromise or remote code execution.

CVE / CNA score 8.1 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
WP File Download
Plugin slug
wp-file-download
Affected
<= 6.3.4
Safe version
See mitigation notes
Published
Sep 02, 2026
Weakness
CWE-22 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

This CVE was published Sep 02, 2026 and is one of 3 known issues for this plugin.

Update, patch or deactivate.

Update to a confirmed release newer than 6.3.4 when available. Until then, disable the affected file-management endpoints or remove the plugin when warranted, verify critical server files, and audit low-privilege account activity.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Primary and upstream sources