CVE-2026-96752: Zero Spam for WordPress · Cross-site Scripting
Affects Zero Spam for WordPressSource CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| bmarshall511Zero Spam for WordPress | Affected
| Fixed in– |
AI-suggested
Users should monitor the vendor's advisory channels for updates. Until a fix is available, consider disabling Contact Form 7 integration or the Zero Spam plugin to prevent exploitation. Implementing web application firewall (WAF) rules to detect and block nested POST array keys with suspicious content may provide temporary mitigation.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/01540d78-ae46-4556-9a7f-3f8b8dbbcbd7?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/zero-spam/tags/5.7.10/includes/templates/admin-modal-details.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/zero-spam/tags/5.7.10/modules/contactform7/class-contactform7.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/zero-spam/tags/5.7.10/core/class-utilities.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/zero-spam/tags/5.7.10/includes/class-db.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3709762%40zero-spam&new=3709762%40zero-spam (opens in a new tab)