{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0620 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0620 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0620 is a medium-severity vulnerability in buildwps PPWP – Password Protect Pages, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-0620 and fix it if it is affected.\n\nWhat it is: CVE-2024-0620 is a medium-severity vulnerability in buildwps PPWP – Password Protect Pages, published on 20 Feb 2024. 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-2024-0620 in the wild and no public exploit code.\n\nAffected product: buildwps PPWP – Password Protect Pages. 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-2024-0620/ (Markdown: https://insights.sbomify.com/CVE-2024-0620/index.md)","id":"CVE-2024-0620","markdown":"https://insights.sbomify.com/CVE-2024-0620/index.md","name":"CVE-2024-0620","record":{"aliases":["GHSA-mvj6-h82m-cjxf"],"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 bypass password protection to access sensitive post metadata via the API.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"password_protect_wordpress","vendor":"passwordprotectwp"}],"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 PPWP – Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.9 via API. This makes it possible for unauthenticated attackers to obtain post titles, IDs, slugs as well as other information including for password-protected posts.","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":"PPWP – Password Protect Pages \u003c= 1.8.9 - Protection Mechanism Bypass","id":"CVE-2024-0620","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Simple Share Buttons Adder \u003c= 8.4.11 - Authenticated(Administrator+) Stored Cross-Site Scripting via CSS Settings","id":"CVE-2024-0621"},"packages":[],"prev":{"headline":"Payflex Payment Gateway \u003c= 2.5.0 - Missing Authorization to Order Status Update","id":"CVE-2024-0619"},"products":["PPWP – Password Protect Pages"],"published":"2024-02-20","related":[{"cvss_score":6.5,"headline":"PPWP \u003c 1.9.11 - Subscriber+ Access Bypass via REST API","id":"CVE-2025-5998","kev_date_added":null,"published":"2025-08-14"},{"cvss_score":5.4,"headline":"PPWP – WordPress Password Protect Page \u003c 1.8.6 - Contributor+ Stored XSS in Shortcode","id":"CVE-2022-4626","kev_date_added":null,"published":"2023-02-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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 bypass password protection to access sensitive post metadata via the API.","url":"https://insights.sbomify.com/CVE-2024-0620/"}