{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0681 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0681 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0681 is a medium-severity vulnerability in cyberlord92 Page and Post Restriction, published on 13 Mar 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-0681 and fix it if it is affected.\n\nWhat it is: CVE-2024-0681 is a medium-severity vulnerability in cyberlord92 Page and Post Restriction, published on 13 Mar 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-0681 in the wild and no public exploit code.\n\nAffected product: cyberlord92 Page and Post Restriction. 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-0681/ (Markdown: https://insights.sbomify.com/CVE-2024-0681/index.md)","id":"CVE-2024-0681","markdown":"https://insights.sbomify.com/CVE-2024-0681/index.md","name":"CVE-2024-0681","record":{"aliases":["GHSA-ccwc-7pw8-r82c"],"analysis":{"component_type":"cms_plugin","fix_type":"workaround","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can view private pages via the REST API due to missing access controls in the Page Restriction WordPress plugin.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"page_restriction","vendor":"miniorange"}],"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-693","name":"Protection Mechanism Failure"}],"description":"The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 1.3.4. This is due to the plugin not properly restricting access to pages via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected pages. The vendor has decided that they will not implement REST API protection on posts and pages and the restrictions will only apply to the front-end of the site. The vendors solution was to add notices throughout the dashboard and recommends installing the WordPress REST API Authentication plugin for REST API coverage.","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":"Page Restriction WordPress (WP) – Protect WP Pages/Post \u003c= 1.3.4 - Protection Mechanism Bypass","id":"CVE-2024-0681","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":"Page Restrict \u003c= 2.5.5 - Protection Mechanism Bypass","id":"CVE-2024-0682"},"packages":[],"prev":{"headline":"WP Private Content Plus \u003c= 3.6 - Protection Mechanism Bypass","id":"CVE-2024-0680"},"products":["Page and Post Restriction"],"published":"2024-03-13","related":[{"cvss_score":5.3,"headline":"Information disclosure in Page and Post Restriction","id":"CVE-2024-11297","kev_date_added":null,"published":"2024-12-20"}],"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":["cyberlord92"]},"summary":"Unauthenticated attackers can view private pages via the REST API due to missing access controls in the Page Restriction WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-0681/"}