Back to CVE records
Medium 5.3Published Aug 13, 2026

CVE-2026-3835Prevent Direct Access – Protect WordPress Files <= 2.8.8.8 - Unauthenticated Protected File Access

Updated under an hour ago ()

Does this affect you?

It affects buildwps Prevent Direct Access – Protect WordPress Files. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Weakness (CWE)
CWE-285
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Wordfence
NVD analysis
Deferred
Record last updated
Aug 13, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
buildwps Prevent Direct Access – Protect WordPress Files
buildwps:prevent_direct_access_protect_wordpress_files (from the name)
through 2.8.8.8
CNA record

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.