HomeWordPress vulnerabilitiesAnti-Spam by CleanTalk
Anti-Spam by CleanTalk vulnerabilities
Anti-Spam by CleanTalk has 5 known vulnerabilities in this database. The most recent published record is dated 5 Sep 2026.
- Known vulnerabilities
- 5
- Active installs
- 200,000+
- Latest version
- 6.88
- Last updated
- 30 Sep 2026
- Most recent
- 5 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-77830 | High 7.2 | Up to 6.86 | Fixed in a later version (latest 6.88) | 5 Sep 2026 |
| Remote code execution CVE-2026-1490 | Critical 9.8 | Up to 6.71 | Fixed in a later version (latest 6.88) | 15 Feb 2026 |
| Remote code execution CVE-2024-10781 | High 8.1 | Before 6.45 | Fixed in 6.45 | 26 Nov 2024 |
| Remote code execution CVE-2024-10542 | Critical 9.8 | Before 6.44 | Fixed in 6.44 | 26 Nov 2024 |
| Cross-site scripting (XSS) CVE-2019-17515 | Medium 6.1 | Before 5.127.4 | Fixed in 5.127.4 | 13 Nov 2019 |
Read the published descriptions
- CVE-2026-77830, 5 Sep 2026
- The Spam protection, Honeypot, Anti-Spam by CleanTalk plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Comment Content aria-label Placeholder in all versions up to, and including, 6.86 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is deliverable via unauthenticated comment submission and executes exclusively for non-logged-in visitors; if comment moderation is enabled, an approving moderator must first publish the comment before the script reaches other users. CVE record
- CVE-2026-1490, 15 Feb 2026
- The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary Plugin Installation due to an authorization bypass via reverse DNS (PTR record) spoofing on the 'checkWithoutToken' function in all versions up to, and including, 6.71. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated. Note: This is only exploitable on sites with an invalid API key. CVE record
- CVE-2024-10781, 26 Nov 2024
- The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary Plugin Installation due to an missing empty value check on the 'api_key' value in the 'perform' function in all versions up to, and including, 6.44. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated. CVE record
- CVE-2024-10542, 26 Nov 2024
- The Spam protection, Anti-Spam, FireWall by CleanTalk plugin for WordPress is vulnerable to unauthorized Arbitrary Plugin Installation due to an authorization bypass via reverse DNS spoofing on the checkWithoutToken function in all versions up to, and including, 6.43.2. This makes it possible for unauthenticated attackers to install and activate arbitrary plugins which can be leveraged to achieve remote code execution if another vulnerable plugin is installed and activated. CVE record
- CVE-2019-17515, 13 Nov 2019
- The CleanTalk cleantalk-spam-protect plugin before 5.127.4 for WordPress is affected by: Cross Site Scripting (XSS). The impact is: Allows an attacker to execute arbitrary HTML and JavaScript code via the from or till parameter. The component is: inc/cleantalk-users.php and inc/cleantalk-comments.php. The attack vector is: When the Administrator is logged in, a reflected XSS may execute upon a click on a malicious URL. CVE record
What to do if you run Anti-Spam by CleanTalk
If you run Anti-Spam by CleanTalk, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Anti-Spam by CleanTalk vulnerabilities
Free. We email you when a new vulnerability is published for Anti-Spam by CleanTalk, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.