{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-6224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-6224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-6224 is a medium-severity cross-site scripting vulnerability in Unknown Send email only on Reply to My Comment, published on 30 Jul 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-6224 and fix it if it is affected.\n\nWhat it is: CVE-2024-6224 is a medium-severity cross-site scripting vulnerability in Unknown Send email only on Reply to My Comment, published on 30 Jul 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-6224 in the wild and no public exploit code.\n\nAffected product: Unknown Send email only on Reply to My Comment. 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-6224/ (Markdown: https://insights.sbomify.com/CVE-2024-6224/index.md)","id":"CVE-2024-6224","markdown":"https://insights.sbomify.com/CVE-2024-6224/index.md","name":"CVE-2024-6224","record":{"aliases":["GHSA-579f-f345-5j7p"],"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":"high_privilege","summary":"Attackers can inject stored XSS payloads via CSRF, allowing admin account takeover in the Send email only on Reply to My Comment plugin.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"send_email_only_on_reply_to_my_comment","vendor":"yasirwazir"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Send email only on Reply to My Comment WordPress plugin through 1.0.6 does not have CSRF check in some places, and is missing sanitisation as well as escaping, which could allow attackers to make logged in admin add Stored XSS payloads via a CSRF attack","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":"Send email only on Reply to My Comment \u003c= 1.0.6 - Stored XSS via CSRF","id":"CVE-2024-6224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Amelia \u003c= 1.1.5 \u0026 Amelia (Pro) \u003c= 7.5.1 - Authenticated (Admin+) Stored Cross-Site Scripting","id":"CVE-2024-6225"},"packages":[],"prev":{"headline":"Send email only on Reply to My Comment \u003c= 1.0.6 - Reflected XSS","id":"CVE-2024-6223"},"products":["Send email only on Reply to My Comment"],"published":"2024-07-30","related":[{"cvss_score":6.1,"headline":"Send email only on Reply to My Comment \u003c= 1.0.6 - Reflected XSS","id":"CVE-2024-6223","kev_date_added":null,"published":"2024-07-30"}],"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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-28","vendors":["Unknown"]},"summary":"Attackers can inject stored XSS payloads via CSRF, allowing admin account takeover in the Send email only on Reply to My Comment plugin.","url":"https://insights.sbomify.com/CVE-2024-6224/"}