Description
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.
References8
- plugins.trac.wordpress.org/browser/prevent-direct-access/tags/2…
- plugins.trac.wordpress.org/browser/prevent-direct-access/trunk/…
- plugins.trac.wordpress.org/browser/prevent-direct-access/trunk/…
- plugins.trac.wordpress.org/changeset/3637499/prevent-direct-acc…
- plugins.trac.wordpress.org/changeset?old_path=%2Fprevent-direct…
- plugins.trac.wordpress.org/changeset?reponame=&new=3637502%40pr…
- wordpress.org/plugins/prevent-direct-access/
- www.wordfence.com/threat-intel/vulnerabilities/id/c39d16f1-ce80…
Metrics
- CVSS 3.1
-
5.3
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - EPSS — exploit probability
- 0% percentile: 41 · as of 12 November 2026
- CWE
- CWE-285
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.