Plugins · paid-downloads · data as of 2026-11-04
Is Paid Downloads safe? Known vulnerabilities and latest version
- Status
- Closed 2026-09-11
- Known issues on record
- 2
- Unpatched in latest
- 0
What to do
- Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
- Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.
With WP-CLI, once you have a replacement: wp plugin deactivate paid-downloads && wp plugin delete paid-downloads
Check your version
Known vulnerabilities
2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.
high 8.1 CVE-2026-87935 · published 2026-09-17
Arbitrary file upload in Paid Downloads (3.15 and older)
- Affected
- 3.15 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The Paid Downloads plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 3.15 via the admin_request_handler function. This is due to missing authorization and file type validation in the admin_request_handler function, which is reachable unauthenticated via is_admin() returning true for /wp-admin/admin-post.php. This makes it possible for unauthenticated attackers to upload files that may be executable, which makes remote code execution possible. On Apache servers where AllowOverride is enabled, an .htaccess file placed in the upload directory may block direct HTTP retrieval of uploaded files, limiting exploitability to stacks that do not honor .htaccess directives such as nginx, LiteSpeed, and Apache with AllowOverride None.
critical 9.3 CVE-2025-68857 · published 2026-01-22
SQL injection in Paid Downloads (3.15 and older)
- Affected
- 3.15 and older
- Fixed in
- unknown
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in ichurakov Paid Downloads paid-downloads allows Blind SQL Injection.This issue affects Paid Downloads: from n/a through <= 3.15.
Recent activity
- 2026-09-11 — closed on wordpress.org.
- 2026-09-17 — Arbitrary file upload disclosed (CVE-2026-87935), fix version not stated.
- 2026-01-22 — SQL injection disclosed (CVE-2025-68857), fix version not stated.
Get an email when Paid Downloads has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for Paid Downloads (paid-downloads) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
Types found in this plugin: Arbitrary file upload (1) · SQL injection (1)
Where this data comes from
- Version, last update, installs, closure: wordpress.org/plugins/paid-downloads (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/paid-downloads"><img src="https://laskyr.com/plugins/paid-downloads/badge.svg" alt="Paid Downloads vulnerability status"></a>