CVE-2026-3835mediumCWE-285

CVE-2026-3835: medium-severity vulnerability in buildwps Prevent Direct Access – Protect…

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

Published

Follow this CVE+ Monitor Prevent Direct Access – Protect WordPress Files

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 5.3epss 0.5%
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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected products
buildwps · Prevent Direct Access – Protect WordPress Files
Related CVEs — buildwps Prevent Direct Access – Protect…

In the same product, most dangerous first.

CVE-2025-3923MEDIUMPrevent Direct Access – Protect WordPress Files <= 2.8.8 - Unauthenticated Sensitive Information ExposureEPSS 0.4%CVE-2025-3861MEDIUMPrevent Direct Access 2.8.6 - 2.8.8.2 - Incorrect Authorization to Authenticated (Contributor+) Multiple Media ActionsEPSS 0.3%