{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-96752 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-96752 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-96752 is a high-severity cross-site scripting vulnerability in bmarshall511 Zero Spam for WordPress, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-96752 and fix it if it is affected.\n\nWhat it is: CVE-2026-96752 is a high-severity cross-site scripting vulnerability in bmarshall511 Zero Spam for WordPress, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-96752 in the wild and no public exploit code.\n\nAffected product: bmarshall511 Zero Spam 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-2026-96752/ (Markdown: https://insights.sbomify.com/CVE-2026-96752/index.md)","id":"CVE-2026-96752","markdown":"https://insights.sbomify.com/CVE-2026-96752/index.md","name":"CVE-2026-96752","record":{"aliases":["GHSA-w7ph-m5xc-pc82"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts via Contact Form 7 submissions, leading to stored XSS execution for users viewing the spam log.","user_interaction":"not_required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The Zero Spam for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Nested POST Array Keys via Contact Form 7 Integration in all versions up to, and including, 5.7.10 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is delivered by submitting a Contact Form 7 request with a nested POST array key containing arbitrary HTML or JavaScript — PHP parses the field name into a nested array key, which is stored verbatim in the zerospam_log.submission_data column when Zero Spam flags the submission as spam due to the absence of the zerospam_david_walsh_key field.","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":"Cross-site scripting in Zero Spam for WordPress","id":"CVE-2026-96752","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"orval @orval/hono before 8.29.0 Code Injection via OpenAPI Path","id":"CVE-2026-96754"},"packages":[],"prev":{"headline":"pmTicket Project-Management-Software add_project.php setSync sql injection","id":"CVE-2026-96751"},"products":["Zero Spam for WordPress"],"published":"2026-09-25","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-25","vendors":["bmarshall511"]},"summary":"Unauthenticated attackers can inject arbitrary scripts via Contact Form 7 submissions, leading to stored XSS execution for users viewing the spam log.","url":"https://insights.sbomify.com/CVE-2026-96752/"}