Prevent Direct Access 2.8.6 - 2.8.8.2 - Incorrect Authorization to Authenticated (Contributor+) Multiple Media Actions
Strategic Overview
- Status
- Patched in 2.8.8.3
- Affected Plugin
- Prevent Direct Access – Protect WordPress Files
- Affected Version
2.8.6 – 2.8.8.2- CVSS
- 5.4Medium
- Weakness type
- CWE-863 · Incorrect Authorization
- CVE
CVE-2025-3861
At a glance
CVE-2025-3861 is a medium-severity Incorrect Authorization vulnerability in the Prevent Direct Access WordPress plugin, affecting versions 2.8.6 – 2.8.8.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.8.8.3; sites on affected versions should update now. Disclosed April 2025, reported by 0xbro.
Vulnerability Overview
The Prevent Direct Access – Protect WordPress Files plugin for WordPress is vulnerable to unauthorized access and modification of data| due to a misconfigured capability check on the 'pda_lite_custom_permission_check' function in versions 2.8.6 to 2.8.8.2. This makes it possible for authenticated attackers, with Contributor-level access and above, to access and change the protection status of media.
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 interaction from a victim user.
CWE-863: Incorrect Authorization
Prevent Direct Access 2.8.6 – 2.8.8.2 carries this weakness at pda_lite_custom_permission_check, and reaching it takes an account at Contributor level or above. Incorrect authorization means a permission check exists but evaluates the wrong thing, so it passes for callers it was meant to stop.
The action runs for users the code intended to exclude, with the same effect as having no check at all. For Prevent Direct Access the fix is 2.8.8.3: builds 2.8.6 – 2.8.8.2 are affected, anything from 2.8.8.3 onward is not.
Remediation
Update to version 2.8.8.3, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Prevent Direct Access 2.8.8.3 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