Live › vulnerability › CVE-2026-109198
Go to dashboardVersions of the Anti-Spam by CleanTalk WordPress plugin up to and including 6.89.1 do not sanitize the user_email parameter. An unauthenticated attacker who registers with a crafted email can plant a script that runs in an administrator's browser when they open the plugin's spam user tabs.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Sites running the Anti-Spam by CleanTalk plugin at version 6.89.1 or earlier with open user registration enabled. The script only fires when an administrator runs the user-spam scan and views the Non-checkable users or Spam users tab, so sites with registration closed or without the plugin can skip it.
No product ranges from the sources yet.
wp plugin get cleantalk-spam-protect --field=version (slug assumed; confirm it).6.89.1, as published by the vendor (fixed version unknown from sources).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-109198")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.