# CVE-2026-96752: Cross-site scripting in Zero Spam for WordPress

> Unauthenticated attackers can inject arbitrary scripts via Contact Form 7 submissions, leading to stored XSS execution for users viewing the spam log.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-w7ph-m5xc-pc82

## What is CVE-2026-96752?

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.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-96752?


## How do I fix CVE-2026-96752?

No fix has been published for CVE-2026-96752 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-96752 being exploited?

There is no known exploitation of CVE-2026-96752 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-96752 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-96752 in the wild and no public exploit code.

Affected product: bmarshall511 Zero Spam for WordPress. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-96752/ (Markdown: https://insights.sbomify.com/CVE-2026-96752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96752
- OSV: https://osv.dev/vulnerability/CVE-2026-96752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-96752/
Summaries are generated and may contain mistakes; the official description above is the record.