CVE-2026-103424
Received Received - Intake

Stored XSS in Anti-Spam by CleanTalk WordPress Plugin

Publication date: 2026-10-10

Last updated on: 2026-10-10

Assigner: Wordfence

Description
The Anti-Spam by CleanTalk – Spam Protection Without CAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment' parameter in all versions up to, and including, 6.88 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. This vulnerability is exploitable once a comment from the attacker's email address has been approved; on default WordPress installations, only the first comment from a given email address is held for moderation, meaning subsequent comments auto-approve and immediately expose the payload to site visitors.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-10
Last Modified
2026-10-10
Generated
2026-10-10
AI Q&A
2026-10-10
EPSS Evaluated
N/A
NVD
CVE-2026-103424
EUVD
EUVD-2026-96064

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
cleantalk Anti-Spam by CleanTalk – Spam Protection Without CAPTCHA 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Anti-Spam by CleanTalk plugin for WordPress. It occurs due to insufficient input sanitization and output escaping in the 'comment' parameter. Unauthenticated attackers can inject malicious scripts into web pages. These scripts execute when users visit the affected pages. The vulnerability is triggered after an attacker's comment is approved, with subsequent comments auto-approving and immediately exposing the payload to visitors.

Detection Guidance

Check WordPress comment logs for suspicious scripts in the 'comment' parameter. Inspect approved comments for injected payloads. Use Wordfence or similar security plugins to scan for XSS patterns in comments.

Impact Analysis

This vulnerability allows attackers to inject malicious scripts into your WordPress site. These scripts can steal user data, hijack sessions, or deface your website. Visitors to your site may have their browsers compromised, leading to potential data breaches or malware infections. The impact includes reputational damage, loss of user trust, and possible legal consequences depending on the data exposed.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA by exposing user data to unauthorized parties. GDPR requires protecting personal data, and a breach could result in fines. HIPAA mandates safeguarding protected health information; a breach here could lead to penalties. The vulnerability increases the risk of data breaches, making compliance more difficult to maintain.

Mitigation Strategies

Update the Anti-Spam by CleanTalk plugin to the latest version. Disable comment approval for subsequent comments from the same email. Implement strict input sanitization for comment fields.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-103424. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart