Anti-Spam by CleanTalk. Spam protection: A security weakness
Anti-Spam by CleanTalk. Spam protection is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 6.79.
- Component
- Anti-Spam by CleanTalk. Spam protection
- Plugin slug
anti-spam-by-cleantalk-spam-protection- Affected
- < 6.79
- Safe version
6.79- Published
- Jun 10, 2026
This CVE was published Jun 10, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Anti-Spam by CleanTalk. Spam protection to 6.79 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The Anti-Spam by CleanTalk. Spam protection WordPress plugin before 6.79 does not properly sanitize content within a custom shortcode used in its email-encoding feature, allowing unauthenticated attackers to inject arbitrary web scripts into approved comments that will execute when any user (including administrators) views the post.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H