CVE-2026-87935: Paid Downloads <= 3.15 - Unauthenticated Arbitrary File Upload via 'paiddownloads_update_file' Action
The Paid Downloads plugin for WordPress is vulnerable to Arbitrary File Upload in all versions up to, and including, 3.15 via the adminrequesthandler function. This is due to missing authorization and file type validation in the adminrequesthandler function, which is reachable unauthenticated via isadmin() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
wordpress/paid-downloadsto a version that resolves this vulnerability.Fixed in 3.15 - Compensating control
On Apache servers where AllowOverride is enabled, ensure uploaded files are not retrievable via direct HTTP by placing an .htaccess file in the upload directory to block direct HTTP retrieval of uploaded files; this mitigation is intended to limit exploitability to stacks that do not honor .htaccess directives such as nginx, LiteSpeed, and Apache with AllowOverride None.
Event History
Frequently Asked Questions
Which deployments are most exposed to remote code execution?
Deployments running Paid Downloads 3.15 or earlier are affected. Exploitability is most significant on nginx, LiteSpeed, and Apache configurations with AllowOverride set to None, because these stacks may not honor an uploaded .htaccess file intended to prevent direct retrieval of uploaded files.
Does an attacker need an account or user interaction to exploit this issue?
No. The vulnerable paiddownloads_update_file action is reachable without authentication through /wp-admin/admin-post.php, and no user interaction is required.
What server configuration may reduce exploitability?
On Apache servers with AllowOverride enabled, an .htaccess file in the upload directory may prevent direct HTTP retrieval of uploaded files. This can limit exploitability, but it does not remove the underlying unauthenticated arbitrary file upload condition.