{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-0615 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-0615 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-0615 is a medium-severity missing authorization vulnerability in danieliser Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More, published on 2 May 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-0615 and fix it if it is affected.\n\nWhat it is: CVE-2024-0615 is a medium-severity missing authorization vulnerability in danieliser Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More, published on 2 May 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-0615 in the wild and no public exploit code.\n\nAffected product: danieliser Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More. 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-0615/ (Markdown: https://insights.sbomify.com/CVE-2024-0615/index.md)","id":"CVE-2024-0615","markdown":"https://insights.sbomify.com/CVE-2024-0615/index.md","name":"CVE-2024-0615","record":{"aliases":["GHSA-8mqw-22hx-c2rj"],"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 access sensitive post information via the API due to missing authorization checks in the Content Control WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"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 Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.0 via the API. This makes it possible for unauthenticated attackers to extract post titles, IDs, slugs, statuses and other information including post content. This includes published content only.","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":"Content Control \u003c= 2.1.0 - Missing Authorization to Sensitive Information Exposure","id":"CVE-2024-0615","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Passster – Password Protect Pages and Content \u003c= 4.2.6.2 - Missing Authorization to Sensitive Information Exposure","id":"CVE-2024-0616"},"packages":[],"prev":{"headline":"Events Manager \u003c= 6.4.6.4 - Authenticated(Administator+) Stored Cross-Site Scripting via settings","id":"CVE-2024-0614"},"products":["Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More"],"published":"2024-05-02","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-04-08","vendors":["danieliser"]},"summary":"Unauthenticated attackers can access sensitive post information via the API due to missing authorization checks in the Content Control WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-0615/"}