Radar sectionsDatabase
Check my site
WordPress plugin

Zero Spam for WordPress <= 5.7.10 — Unauthenticated Stored Cross-Site Scripting via Nested POST Array Keys via Contact Form 7 Integration

CVE-2026-96752Published · Updated

Action summary

Affected: ≤5.7.10Update to 5.7.11 or newer

All remediation steps
Severity
High7.2
CVSS
7.2
CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
What does this vector mean?
AV:N Attack vector
Network
AC:L Attack complexity
Low
PR:N Privileges required
None
UI:N User interaction
None
S:C Scope
Changed
C:L Confidentiality
Low
I:L Integrity
Low
A:N Availability
None
Weakness
CWE-79 Cross-Site Scripting
Required access
No account needed
Exploit prediction (EPSS)
No score
CISA KEV
Not listed

Am I affected?

Zero Spam for WordPress zero-spam

  1. Affected≤ 5.7.10
  2. Patched in5.7.11

Update to 5.7.11 or newer.

You are affected if you run ≤ 5.7.10. Version 5.7.11 and later are not affected by this issue.

  • Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under Zero Spam for WordPress.
  • No admin access? Run a passive check of your site. It reads public files only.
  • No account is needed to exploit this. Treat any exposed site on an affected version as at risk.

What to do

  1. Update to version 5.7.11, or a newer patched version
  2. Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
  3. Watch Zero Spam for WordPress to get an email when the next vulnerability is published.

Advisory

Source description from Wordfence Intelligence, credited to Adrien Brunner.

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.

Exploits & references

Proof-of-concept & detection

No public proof-of-concept or detection template is known for this vulnerability.

Advisories & patches

More in Zero Spam for WordPress

All 7
More vulnerabilities in Zero Spam for WordPress
SeverityVulnerabilityCVEPublished
Medium5.3Unauthenticated Spam Protection Bypass on Login
≤5.7.11Update to 5.7.12
CVE-2026-105057
Medium5.3Spam Protection Bypass
≤5.5.6Update to 5.5.7
CVE-2024-32521
High7.2Authenticated (Administrator+) SQL Injection
≤5.4.4Update to 5.4.5
CVE-2023-32121
High7.2Authenticated(Administrator+) SQL Injection
<5.4.5Update to 5.4.5
—
High7.2Admin+ SQL Injection
≤5.2.10Update to 5.2.11
CVE-2022-0254

Same weakness (Cross-Site Scripting)

All Cross-Site Scripting
Other Cross-Site Scripting vulnerabilities
SeverityVulnerabilityCVEPublished
High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent HeaderCVE-2026-120688
Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form SubmissionCVE-2026-125055
Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' ParameterCVE-2026-119077
Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce≤5.127.0Update to 5.128.0
CVE-2026-121518

Timeline

  1. CVE published

    Severity high, CVSS 7.2

  2. Record last updated

Sources & licenses

Wordfence record
Vulnerability data
Wordfence Intelligence. [object Object] Licensed under the CC BY-SA 4.0.
CVE® identifiers
[object Object]. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
CVSS / CWE
National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
VulnCrest content
Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.

How we use these sources

Search VulnCrest Radar

Are you sure?