{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1911 exists.","fix":"No fix has been published for CVE-2023-1911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-1911 is a medium-severity missing authorization vulnerability in Unknown Blocksy Companion, published on 2 May 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-1911 and fix it if it is affected.\n\nWhat it is: CVE-2023-1911 is a medium-severity missing authorization vulnerability in Unknown Blocksy Companion, published on 2 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-1911 exists.\n\nAffected product: Unknown Blocksy Companion. 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-2023-1911/ (Markdown: https://insights.sbomify.com/CVE-2023-1911/index.md)","id":"CVE-2023-1911","markdown":"https://insights.sbomify.com/CVE-2023-1911/index.md","name":"CVE-2023-1911","record":{"aliases":["GHSA-v7cp-3qx6-ff4r"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can access draft posts via shortcode due to missing authorization checks in the Blocksy Companion plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"blocksy_companion","vendor":"creativethemes"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"The Blocksy Companion WordPress plugin before 1.8.82 does not ensure that posts to be accessed via a shortcode are already public and can be viewed, allowing any authenticated users, such as subscriber to access draft posts for example","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Blocksy Companion \u003c 1.8.82 - Subscriber+ Draft Post Access","id":"CVE-2023-1911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Limit Login Attempts \u003c= 1.7.1 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2023-1912"},"packages":[],"prev":{"headline":"Getwid – Gutenberg Blocks \u003c= 1.8.3 - Improper Authorization via get_remote_templates REST endpoint","id":"CVE-2023-1910"},"products":["Blocksy Companion"],"published":"2023-05-02","related":[{"cvss_score":6.4,"headline":"Blocksy Companion \u003c= 2.0.45 - Authenticated (Contributor+) Stored Cross-Site Scripting via SVG Uploads","id":"CVE-2024-4487","kev_date_added":null,"published":"2024-05-11"},{"cvss_score":6.4,"headline":"Blocksy Companion \u003c= 2.0.31 - Authenticated (Contributor+) Stored Cross-Site Scripting","id":"CVE-2024-2392","kev_date_added":null,"published":"2024-03-22"},{"cvss_score":5.5,"headline":"WordPress Blocksy Companion Plugin \u003c= 1.8.67 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-23898","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":5.4,"headline":"WordPress Blocksy Companion plugin \u003c= 2.0.28 - Cross Site Request Forgery (CSRF) vulnerability","id":"CVE-2024-31932","kev_date_added":null,"published":"2024-04-11"},{"cvss_score":4.4,"headline":"WordPress Blocksy Companion plugin \u003c= 2.0.42 - Server Side Request Forgery (SSRF) vulnerability","id":"CVE-2024-35633","kev_date_added":null,"published":"2024-06-03"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-30","vendors":["Unknown"]},"summary":"Authenticated users can access draft posts via shortcode due to missing authorization checks in the Blocksy Companion plugin.","url":"https://insights.sbomify.com/CVE-2023-1911/"}