{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3201 exists.","fix":"No fix has been published for CVE-2025-3201 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3201 is a medium-severity cross-site scripting vulnerability in Unknown Contact Form builder with drag \u0026 drop for WordPress, published on 16 May 2025. 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-2025-3201 and fix it if it is affected.\n\nWhat it is: CVE-2025-3201 is a medium-severity cross-site scripting vulnerability in Unknown Contact Form builder with drag \u0026 drop for WordPress, published on 16 May 2025. An attacker needs administrator access to exploit it, 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-2025-3201 exists.\n\nAffected product: Unknown Contact Form builder with drag \u0026 drop for WordPress. 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-2025-3201/ (Markdown: https://insights.sbomify.com/CVE-2025-3201/index.md)","id":"CVE-2025-3201","markdown":"https://insights.sbomify.com/CVE-2025-3201/index.md","name":"CVE-2025-3201","record":{"aliases":["GHSA-qqv4-m5cq-pp99"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"high_privilege","summary":"Contributors can inject malicious scripts into form settings, leading to stored XSS attacks against other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"kali_forms","vendor":"kaliforms"}],"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 Contact Form builder with drag \u0026 drop for WordPress  WordPress plugin before 2.4.3 does not sanitise and escape some of its settings, which could allow high privilege users such as contributors to perform Stored Cross-Site Scripting attacks.","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":"Kali Forms \u003c 2.4.3 - Contributor+ Stored XSS","id":"CVE-2025-3201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"ageerle ruoyi-ai SysNoticeController.java improper authorization","id":"CVE-2025-3202"},"packages":[],"prev":{"headline":"Com-Server Exposed via Weak TLS","id":"CVE-2025-3200"},"products":["Contact Form builder with drag \u0026 drop for WordPress"],"published":"2025-05-16","related":[{"cvss_score":8.8,"headline":"Kali Forms \u003c= 2.1.1 - Cross-Site Request Forgery","id":"CVE-2020-36717","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.6,"headline":"Kali Forms \u003c= 2.1.1 - Unauthenticated Arbitrary Post Deletion","id":"CVE-2020-36712","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":7.5,"headline":"Missing authorization in Contact Form builder with drag \u0026 drop for WordPress – Kali Forms","id":"CVE-2024-22305","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":7.1,"headline":"Kali Forms \u003c= 2.1.1 - Missing Authorization to Settings Update","id":"CVE-2020-36720","kev_date_added":null,"published":"2023-06-07"}],"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-16","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts into form settings, leading to stored XSS attacks against other users.","url":"https://insights.sbomify.com/CVE-2025-3201/"}