Prevent Direct Access – Protect WordPress Files: Sensitive information exposure
Prevent Direct Access – Protect WordPress Files is affected by sensitive information exposure. The vulnerable path is reachable without authentication. Successful exploitation can disclose data that should not be available to the caller.
- Component
- Prevent Direct Access – Protect WordPress Files
- Plugin slug
prevent-direct-access- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Apr 25, 2025
This CVE was published Apr 25, 2025 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update Prevent Direct Access – Protect WordPress Files to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Prevent Direct Access – Protect WordPress Files plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.8.8 via the 'generate_unique_string' due to insufficient randomness of the generated file name. This makes it possible for unauthenticated attackers to extract sensitive data including files protected by the plugin if the attacker can determine the file name.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N