CVE-2025-3923

Prevent Direct Access – Protect WordPress Files <= 2.8.8 - Unauthenticated Sensitive Information Exposure

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.

Category

5.3
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.05%
Affected: buildwps Prevent Direct Access – Protect WordPress Files
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2025-3923?
CVE-2025-3923 has been scored as a medium severity vulnerability.
How to fix CVE-2025-3923?
To fix CVE-2025-3923, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2025-3923 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-3923 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-3923?
CVE-2025-3923 affects buildwps Prevent Direct Access – Protect WordPress Files.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.