{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-53712 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-53712 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-53712 is a high-severity cross-site scripting vulnerability in kevmimcc Kevin's, published on 2 Dec 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-53712 and fix it if it is affected.\n\nWhat it is: CVE-2024-53712 is a high-severity cross-site scripting vulnerability in kevmimcc Kevin's, published on 2 Dec 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: There is no known exploitation of CVE-2024-53712 in the wild and no public exploit code.\n\nAffected product: kevmimcc Kevin's. 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-53712/ (Markdown: https://insights.sbomify.com/CVE-2024-53712/index.md)","id":"CVE-2024-53712","markdown":"https://insights.sbomify.com/CVE-2024-53712/index.md","name":"CVE-2024-53712","record":{"aliases":["GHSA-xmr8-m3g7-8q7w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can exploit CSRF to inject stored XSS payloads, potentially hijacking user sessions or executing malicious scripts in WordPress.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability in kevmimcc Kevin's kevins-plugin allows Stored XSS.This issue affects Kevin's: from n/a through \u003c= 2.0.0.","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":"WordPress Kevin's plugin \u003c= 2.0.0 - CSRF to Stored XSS vulnerability","id":"CVE-2024-53712","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Silverlight Video Player plugin \u003c= 1.0 - CSRF to Stored XSS vulnerability","id":"CVE-2024-53713"},"packages":[],"prev":{"headline":"WordPress Hotlink2Watermark plugin \u003c= 0.3.2 - CSRF to Stored XSS vulnerability","id":"CVE-2024-53711"},"products":["Kevin's"],"published":"2024-12-02","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["kevmimcc"]},"summary":"Attackers can exploit CSRF to inject stored XSS payloads, potentially hijacking user sessions or executing malicious scripts in WordPress.","url":"https://insights.sbomify.com/CVE-2024-53712/"}