{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3149 exists.","fix":"No fix has been published for CVE-2022-3149 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-3149 is a medium-severity cross-site scripting vulnerability in Unknown WP Custom Cursors, published on 17 Oct 2022. 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-3149 and fix it if it is affected.\n\nWhat it is: CVE-2022-3149 is a medium-severity cross-site scripting vulnerability in Unknown WP Custom Cursors, published on 17 Oct 2022. 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-3149 exists.\n\nAffected product: Unknown WP Custom Cursors. 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-3149/ (Markdown: https://insights.sbomify.com/CVE-2022-3149/index.md)","id":"CVE-2022-3149","markdown":"https://insights.sbomify.com/CVE-2022-3149/index.md","name":"CVE-2022-3149","record":{"aliases":["GHSA-h8r9-x743-rhhc"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts via CSRF in WP Custom Cursors, allowing admin account takeover or site compromise.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"wp_custom_cursors","vendor":"wp_custom_cursors_project"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The WP Custom Cursors WordPress plugin before 3.0.1 does not have CSRF check in place when creating and editing cursors, which could allow attackers to made a logged in admin perform such actions via CSRF attacks. Furthermore, due to the lack of sanitisation and escaping in some of the cursor options, it could also lead to Stored Cross-Site Scripting","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":"WP Custom Cursors \u003c 3.0.1 - Stored Cross-Site Scripting via CSRF","id":"CVE-2022-3149","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"WP Custom Cursors \u003c 3.2 - Admin+ SQLi","id":"CVE-2022-3150"},"packages":[],"prev":{"headline":"Cross-site Scripting (XSS) - Generic in jgraph/drawio","id":"CVE-2022-3148"},"products":["WP Custom Cursors"],"published":"2022-10-17","related":[{"cvss_score":7.2,"headline":"WP Custom Cursors \u003c 3.2 - Admin+ SQLi","id":"CVE-2023-2221","kev_date_added":null,"published":"2023-06-19"},{"cvss_score":7.2,"headline":"WP Custom Cursors \u003c 3.2 - Admin+ SQLi","id":"CVE-2022-3150","kev_date_added":null,"published":"2022-10-17"},{"cvss_score":4.3,"headline":"WP Custom Cursors \u003c 3.0.1 - Arbitrary Cursor Deletion via CSRF","id":"CVE-2022-3151","kev_date_added":null,"published":"2022-10-17"}],"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-05-14","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts via CSRF in WP Custom Cursors, allowing admin account takeover or site compromise.","url":"https://insights.sbomify.com/CVE-2022-3149/"}