CVE-2026-8071: Anti-Spam by CleanTalk. Spam protection (WordPress plugin) · Cross-Site Scripting (XSS)
Affects Anti-Spam by CleanTalk. Spam protection (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 6.79 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.79
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Jun 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 30 Oct 2026.
What to do
Upgrade Anti-Spam by CleanTalk. Spam protection (WordPress plugin) to 6.79.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Anti-Spam by CleanTalk. Spam protection | Affected
| Fixed in
|
AI-suggested
Since the vulnerability affects versions before 6.79, upgrading to version 6.79 or later is likely the intended remediation once officially released. Until then, restrict comment approvals and monitor for suspicious activity related to comment content. Avoid interacting with untrusted comments containing the vulnerable shortcode.
Description
A Cross-Site Scripting (XSS) vulnerability exists in the Anti-Spam by CleanTalk WordPress plugin before version 6.79. The issue arises from improper sanitization of content within a custom shortcode used in the email-encoding feature. This allows unauthenticated attackers to inject arbitrary scripts into approved comments, which execute when any user views the affected post, including administrators.