HomeWordPress vulnerabilitiesWP File Download
WP File Download vulnerabilities
WP File Download has 3 known vulnerabilities in this database. The most recent published record is dated 10 Oct 2026.
- Known vulnerabilities
- 3
- Active installs
- Not listed
- Latest version
- Unknown
- Last updated
- Unknown
- Most recent
- 10 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-39799 | High 7.1 | Up to 6.3.6 | Check for an update | 2 d ago |
| Path traversal CVE-2026-14975 | Medium 6.5 | Up to 6.3.8 | Check for an update | 5 Sep 2026 |
| Cross-site scripting (XSS) CVE-2025-5034 | High 7.1 | Before 6.2.6 | Fixed in 6.2.6 | 21 Jun 2025 |
Read the published descriptions
- CVE-2026-39799, 10 Oct 2026
- Unauthenticated Cross Site Scripting (XSS) in WP File Download <= 6.3.6 versions. CVE record
- CVE-2026-14975, 5 Sep 2026
- 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 makes it possible for 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 with Subscriber-level access 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. CVE record
- CVE-2025-5034, 21 Jun 2025
- The wp-file-download WordPress plugin before 6.2.6 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting CVE record
What to do if you run WP File Download
If you run WP File Download, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP File Download vulnerabilities
Free. We email you when a new vulnerability is published for WP File Download, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.