CVE-2026-109198: CleanTalk Anti-Spam (WordPress plugin) · Cross-site Scripting
Affects CleanTalk Anti-Spam (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 14:00 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 31% 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 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| cleantalkCleanTalk Anti-Spam – Complete Spam Protection | Affected
| Fixed in– |
AI-suggested
Users should check the vendor advisory for updates. Until a fix is available, it is recommended to disable user registration if not needed and restrict administrator access to the plugin's user-spam scan interface. Monitoring for plugin updates and applying them promptly when released is advised.
Description
The Anti-Spam by CleanTalk – Spam Protection Without CAPTCHA plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'user_email' parameter in all versions up to, and including, 6.89.1 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. Successful exploitation requires user registration to be open on the site, and script execution is triggered when an Administrator subsequently runs the plugin's user-spam scan and views the resulting Non-checkable users or Spam users tab — the plugin's own documented workflow.
References
- wordfence.com/threat-intel/vulnerabilities/id/93cf8a35-61a4-4998-ae34-86c96898e30f?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/cleantalk-spam-protect/tags/6.89.1/lib/Cleantalk/ApbctWP/FindSpam/ListTable/BadUsers.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/cleantalk-spam-protect/tags/6.89.1/lib/Cleantalk/ApbctWP/FindSpam/ListTable/Users.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/cleantalk-spam-protect/tags/6.89.1/lib/Cleantalk/ApbctWP/FindSpam/UsersChecker.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/cleantalk-spam-protect/tags/6.89.1/inc/cleantalk-public-integrations.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3747972%40cleantalk-spam-protect&new=3747972%40cleantalk-spam-protect (opens in a new tab)