Prevent Direct Access – Protect WordPress Files <= 2.8.8.8 - Unauthenticated Protected File Access
Strategic Overview
- Status
- Patched in 2.8.8.9
- Affected Plugin
- Prevent Direct Access – Protect WordPress Files
- Affected Version
<= 2.8.8.8- CVSS
- 5.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2026-3835
At a glance
CVE-2026-3835 is a medium-severity Improper Authorization vulnerability in the Prevent Direct Access WordPress plugin, affecting versions <= 2.8.8.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.8.8.9; sites on affected versions should update now. Disclosed August 2026, reported by Lucas Montes (NiRoX).
Vulnerability Overview
The Prevent Direct Access – Protect WordPress Files plugin for WordPress is vulnerable to unauthorized access of protected files due to insufficient token validation in the `get_advance_file_by_url()` method in all versions up to, and including, 2.8.8.8 The method uses a SQL `LIKE` operator for token lookup without escaping wildcard characters via `$wpdb->esc_like()`. This makes it possible for unauthenticated attackers to bypass the private token requirement by supplying SQL wildcard characters (such as `%`) as the token value, matching any record in the plugin's file table and downloading any protected file.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-285: Improper Authorization
Prevent Direct Access <= 2.8.8.8 carries this weakness at get_advance_file_by_url(), and reaching it takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Prevent Direct Access the fix is 2.8.8.9: builds <= 2.8.8.8 are affected, anything from 2.8.8.9 onward is not.
Remediation
Update to version 2.8.8.9, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Prevent Direct Access 2.8.8.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Prevent Direct Access – Protect WordPress Files
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C