{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6023 exists.","fix":"No fix has been published for CVE-2024-6023 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6023 is a high-severity vulnerability in Unknown ContentLock, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-6023 and fix it if it is affected.\n\nWhat it is: CVE-2024-6023 is a high-severity vulnerability in Unknown ContentLock, published on 12 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6023 exists.\n\nAffected product: Unknown ContentLock. 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-6023/ (Markdown: https://insights.sbomify.com/CVE-2024-6023/index.md)","id":"CVE-2024-6023","markdown":"https://insights.sbomify.com/CVE-2024-6023/index.md","name":"CVE-2024-6023","record":{"aliases":["GHSA-ppc6-pqcq-584g"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can force logged-in admins to add emails via CSRF due to missing checks in the ContentLock WordPress plugin.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"contentlock","vendor":"adamsolymosi"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which could allow attackers to make a logged in admin perform such action via a CSRF attack","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":"ContentLock \u003c= 1.0.3 - Email Adding via CSRF","id":"CVE-2024-6023","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"ContentLock \u003c= 1.0.3 - Groups/Emails Deletion via CSRF","id":"CVE-2024-6024"},"packages":[],"prev":{"headline":"ContentLock \u003c= 1.0.3 - Settings Update via CSRF","id":"CVE-2024-6022"},"products":["ContentLock"],"published":"2024-07-12","related":[{"cvss_score":8.8,"headline":"ContentLock \u003c= 1.0.3 - Settings Update via CSRF","id":"CVE-2024-6022","kev_date_added":null,"published":"2024-07-12"},{"cvss_score":8.8,"headline":"ContentLock \u003c= 1.0.3 - Groups/Emails Deletion via CSRF","id":"CVE-2024-6024","kev_date_added":null,"published":"2024-07-12"}],"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":"total"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["Unknown"]},"summary":"Attackers can force logged-in admins to add emails via CSRF due to missing checks in the ContentLock WordPress plugin.","url":"https://insights.sbomify.com/CVE-2024-6023/"}