CVE-2026-109198 cleantalk CVE debrief

Who should care

Defenders responsible for WordPress sites using the Anti-Spam by CleanTalk plugin should assess exposure to this vulnerability, especially if user registration is open on the site. They should also review the plugin's user-spam scan workflow and ensure that Administrators are cautious when viewing the Non-checkable users or Spam users tab.

Why it matters

The Anti-Spam by CleanTalk plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'user_email' parameter, allowing unauthenticated attackers to inject arbitrary web scripts. Defenders should assess exposure, review the plugin's user-spam scan workflow, and ensure cautious Administrator actions to prevent potential script execution.

• Defenders need to verify if user registration is open on the site to assess exposure.
• Administrators may be affected when viewing the Non-checkable users or Spam users tab after running the plugin's user-spam scan.
• The vulnerability requires user registration to be open on the site, limiting the attack surface.
• Remediation priority is moderate, as the vulnerability is publicly known and could be targeted.

Technical summary

The Anti-Spam by CleanTalk plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'user_email' parameter in versions up to, and including, 6.89.1. This vulnerability allows unauthenticated attackers to inject arbitrary web scripts, which can be executed when an Administrator views the Non-checkable users or Spam users tab after running the plugin's user-spam scan. 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. Defenders should prioritize verifying if user  

Defensive priority

Defenders should prioritize verifying if user registration is open on the site and assess exposure to this vulnerability. They should also review the plugin's user-spam scan workflow and ensure that Administrators are cautious when viewing the Non-checkable users or Spam users tab.

Recommended defensive actions

• Verify if user registration is open on the site
• Review the plugin's user-spam scan workflow
• Ensure Administrators are cautious when viewing the Non-checkable users or Spam users tab
• Consider updating the plugin to a version that addresses this vulnerability
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including the affected versions and the required conditions for exploitation. However, the corpus does not provide information on known affected scope, inventory checks, or vendor remediation.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.