{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-12000 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12000 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12000 is a high-severity missing authorization vulnerability in cyberlord92 Page and Post Restriction, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-12000 and fix it if it is affected.\n\nWhat it is: CVE-2026-12000 is a high-severity missing authorization vulnerability in cyberlord92 Page and Post Restriction, published on 5 Aug 2026. 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-2026-12000 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-2026-12000/ (Markdown: https://insights.sbomify.com/CVE-2026-12000/index.md)","id":"CVE-2026-12000","markdown":"https://insights.sbomify.com/CVE-2026-12000/index.md","name":"CVE-2026-12000","record":{"aliases":["GHSA-j2cm-38v7-pfcv"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can read private page and post content via REST API when global privacy toggles are enabled, bypassing frontend restrictions.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Page and Post Restriction plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to and including 1.4.0 via the WordPress core REST endpoints /wp-json/wp/v2/pages, /wp-json/wp/v2/pages/\u003cid\u003e, /wp-json/wp/v2/posts, and /wp-json/wp/v2/posts/\u003cid\u003e. This is due to the plugin's REST guards — papr_restrict_page_post_rest_api() and the the_posts filter registered by papr_filter_posts() — sourcing their restricted-ID list exclusively from papr_get_restricted_posts_id(), which only reads the per-page metabox options papr_allowed_redirect_for_pages and papr_allowed_redirect_for_posts and never consults the two global toggles papr_access_for_only_loggedin and papr_access_for_only_loggedin_posts that the plugin's own UI describes as 'Make all Pages Private' / 'Make all Posts Private'. This makes it possible for unauthenticated attackers to read the full rendered content of every published page and post on sites configured with the documented global toggles, bypassing the security boundary enforced on the frontend by papr_restrict_logged_in_users().","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":"Missing authorization in Page and Post Restriction","id":"CVE-2026-12000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Hardcoded Credential Vulnerability in Multiple TP-Link Router Models","id":"CVE-2026-12001"},"packages":[],"prev":{"headline":"X.509 trust-chain bypass via path-depth exhaustion in wolfSSL_X509_verify_cert()","id":"CVE-2026-11999"},"products":["Page and Post Restriction"],"published":"2026-08-05","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-08-05","vendors":["cyberlord92"]},"summary":"Unauthenticated attackers can read private page and post content via REST API when global privacy toggles are enabled, bypassing frontend restrictions.","url":"https://insights.sbomify.com/CVE-2026-12000/"}