{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-1760 exists.","fix":"No fix has been published for CVE-2022-1760 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-1760 is a medium-severity vulnerability in Unknown Core Control, published on 16 Jan 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-2022-1760 and fix it if it is affected.\n\nWhat it is: CVE-2022-1760 is a medium-severity vulnerability in Unknown Core Control, published on 16 Jan 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-2022-1760 exists.\n\nAffected product: Unknown Core Control. 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-2022-1760/ (Markdown: https://insights.sbomify.com/CVE-2022-1760/index.md)","id":"CVE-2022-1760","markdown":"https://insights.sbomify.com/CVE-2022-1760/index.md","name":"CVE-2022-1760","record":{"aliases":["GHSA-x93g-3xq3-cp8q"],"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 trick logged-in admins into changing Core Control plugin settings via CSRF, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"core_control","vendor":"dd32"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The Core Control WordPress plugin through 1.2.1 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them 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":"Core Control \u003c= 1.2.1 - Arbitrary Settings Update via CSRF","id":"CVE-2022-1760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Peter’s Collaboration E-mails \u003c= 2.2.0 - Arbitrary Settings Update via CSRF","id":"CVE-2022-1761"},"packages":[],"prev":{"headline":"RB Internal Links \u003c= 2.0.16 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-1759"},"products":["Core Control"],"published":"2024-01-16","related":[],"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-06-02","vendors":["Unknown"]},"summary":"Attackers can trick logged-in admins into changing Core Control plugin settings via CSRF, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2022-1760/"}