{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-3923 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3923 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3923 is a medium-severity vulnerability in buildwps Prevent Direct Access – Protect WordPress Files, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-3923 and fix it if it is affected.\n\nWhat it is: CVE-2025-3923 is a medium-severity vulnerability in buildwps Prevent Direct Access – Protect WordPress Files, published on 25 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-3923 in the wild and no public exploit code.\n\nAffected product: buildwps Prevent Direct Access – Protect WordPress Files. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-3923/ (Markdown: https://insights.sbomify.com/CVE-2025-3923/index.md)","id":"CVE-2025-3923","markdown":"https://insights.sbomify.com/CVE-2025-3923/index.md","name":"CVE-2025-3923","record":{"aliases":["GHSA-3jr3-8hm5-hxqw"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can extract protected files by guessing predictable filenames due to insufficient randomness in the Prevent Direct Access plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Prevent Direct Access – Protect WordPress Files \u003c= 2.8.8 - Unauthenticated Sensitive Information Exposure","id":"CVE-2025-3923","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"PeproDev Ultimate Profile Solutions 1.9.1 - 7.5.2 - Missing Authorization to Unauthenticated Email Enumeration","id":"CVE-2025-3924"},"packages":[],"prev":{"headline":"Allocation of Resources Without Limits or Throttling in GitLab","id":"CVE-2025-3922"},"products":["Prevent Direct Access – Protect WordPress Files"],"published":"2025-04-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["buildwps"]},"summary":"Unauthenticated attackers can extract protected files by guessing predictable filenames due to insufficient randomness in the Prevent Direct Access plugin.","url":"https://insights.sbomify.com/CVE-2025-3923/"}