{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-0680 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0680 is a medium-severity missing authorization vulnerability in nimeshrmr WP Private Content Plus, published on 28 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-0680 and fix it if it is affected.\n\nWhat it is: CVE-2024-0680 is a medium-severity missing authorization vulnerability in nimeshrmr WP Private Content Plus, published on 28 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-0680 in the wild and no public exploit code.\n\nAffected product: nimeshrmr WP Private Content Plus. 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-0680/ (Markdown: https://insights.sbomify.com/CVE-2024-0680/index.md)","id":"CVE-2024-0680","markdown":"https://insights.sbomify.com/CVE-2024-0680/index.md","name":"CVE-2024-0680","record":{"aliases":["GHSA-x7m4-p3pg-xrfm"],"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 view private posts via the REST API due to improper access restrictions in the WP Private Content Plus plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"wp_private_content_plus","vendor":"wpexpertdeveloper"}],"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 WP Private Content Plus plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 3.6. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view 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":"WP Private Content Plus \u003c= 3.6 - Protection Mechanism Bypass","id":"CVE-2024-0680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":3,"next":{"headline":"Page Restriction WordPress (WP) – Protect WP Pages/Post \u003c= 1.3.4 - Protection Mechanism Bypass","id":"CVE-2024-0681"},"packages":[],"prev":{"headline":"ColorMag \u003c= 3.1.2 - Missing Authorization to Arbitrary Plugin Installation","id":"CVE-2024-0679"},"products":["WP Private Content Plus"],"published":"2024-02-28","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2019-15816","kev_date_added":null,"published":"2019-08-30"},{"cvss_score":4.3,"headline":"WP Private Content Plus \u003c= 3.1 - Cross-Site Request Forgery Bypass","id":"CVE-2021-4385","kev_date_added":null,"published":"2023-07-01"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["nimeshrmr"]},"summary":"Unauthenticated attackers can view private posts via the REST API due to improper access restrictions in the WP Private Content Plus plugin.","url":"https://insights.sbomify.com/CVE-2024-0680/"}