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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 8
https://plugins.trac.wordpress.org/browser/prevent-direct-access/tags/2.8.8.4/i…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/prevent-direct-access/trunk/download…
security@wordfence.com
https://plugins.trac.wordpress.org/browser/prevent-direct-access/trunk/includes…
security@wordfence.com
https://plugins.trac.wordpress.org/changeset/3637499/prevent-direct-access/trun…
security@wordfence.com
https://plugins.trac.wordpress.org/changeset?old_path=%2Fprevent-direct-access/…
security@wordfence.com
https://plugins.trac.wordpress.org/changeset?reponame=&new=3637502%40prevent-di…
security@wordfence.com
https://wordpress.org/plugins/prevent-direct-access/
security@wordfence.com
https://www.wordfence.com/threat-intel/vulnerabilities/id/c39d16f1-ce80-402c-8a…
security@wordfence.com