{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-11153 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-11153 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-11153 is a medium-severity vulnerability in danieliser Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More, published on 5 Mar 2025. 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-11153 and fix it if it is affected.\n\nWhat it is: CVE-2024-11153 is a medium-severity vulnerability in danieliser Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More, published on 5 Mar 2025. 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-11153 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-11153/ (Markdown: https://insights.sbomify.com/CVE-2024-11153/index.md)","id":"CVE-2024-11153","markdown":"https://insights.sbomify.com/CVE-2024-11153/index.md","name":"CVE-2024-11153","record":{"aliases":["GHSA-w5c3-9ghv-4x89"],"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 restricted posts.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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.5.0 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 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":"Information disclosure in Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More","id":"CVE-2024-11153","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":"Missing authorization in PublishPress Revisions: Duplicate Posts, Submit, Approve and Schedule Content Changes","id":"CVE-2024-11154"},"packages":[],"prev":{"headline":"WordPress User Extra Fields \u003c= 16.6 - Unauthenticated Arbitrary File Deletion","id":"CVE-2024-11150"},"products":["Content Control – The Ultimate Content Restriction Plugin! Restrict Content, Create Conditional Blocks \u0026 More"],"published":"2025-03-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-04-08","vendors":["danieliser"]},"summary":"Unauthenticated attackers can bypass content restrictions via WordPress search to expose sensitive data from restricted posts.","url":"https://insights.sbomify.com/CVE-2024-11153/"}