{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-11297 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-11297 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11297 is a medium-severity vulnerability in cyberlord92 Page and Post Restriction, published on 20 Dec 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-11297 and fix it if it is affected.\n\nWhat it is: CVE-2024-11297 is a medium-severity vulnerability in cyberlord92 Page and Post Restriction, published on 20 Dec 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-11297 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-11297/ (Markdown: https://insights.sbomify.com/CVE-2024-11297/index.md)","id":"CVE-2024-11297","markdown":"https://insights.sbomify.com/CVE-2024-11297/index.md","name":"CVE-2024-11297","record":{"aliases":["GHSA-wfqx-gh2p-77p7"],"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 content restrictions via WordPress search to expose sensitive data from administrator-only posts in the Page Restriction 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-203","name":"Observable Discrepancy"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The Page Restriction WordPress (WP) – Protect WP Pages/Post plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.3.6 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator.","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":"Information disclosure in Page and Post Restriction","id":"CVE-2024-11297","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-11298"},"packages":[],"prev":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2024-11296"},"products":["Page and Post Restriction"],"published":"2024-12-20","related":[{"cvss_score":5.3,"headline":"Page Restriction WordPress (WP) – Protect WP Pages/Post \u003c= 1.3.4 - Protection Mechanism Bypass","id":"CVE-2024-0681","kev_date_added":null,"published":"2024-03-13"}],"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 bypass content restrictions via WordPress search to expose sensitive data from administrator-only posts in the Page Restriction plugin.","url":"https://insights.sbomify.com/CVE-2024-11297/"}