Spam protection, Honeypot, Anti-Spam by CleanTalk <= 6.71 - Authorization Bypass via Reverse DNS (PTR record) Spoofing to Unauthenticated Arbitrary Plugin Installation
Strategic Overview
- Status
- Patched in 6.72
- Affected Plugin
- Spam protection, Honeypot, Anti-Spam by CleanTalk
- Affected Version
<= 6.71- CVSS
- 9.8Critical
- Weakness type
- CWE-350 · Reliance on Reverse DNS Resolution for a Security-Critical Action
- CVE
CVE-2026-1490
At a glance
CVE-2026-1490 is a critical-severity Reliance on Reverse DNS Resolution for a Security-Critical Action vulnerability in the Spam protection, Honeypot, Anti-Spam by CleanTalk WordPress plugin, affecting versions <= 6.71. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 6.72; sites on affected versions should update now. Disclosed February 2026, reported by Nguyen Ngoc Duc (duc193).
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-350: Reliance on Reverse DNS Resolution for a Security-Critical Action
The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.
Remediation
Update to version 6.72, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Spam protection, Honeypot, Anti-Spam by CleanTalk 6.72 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Spam protection, Honeypot, Anti-Spam by CleanTalk
- 9.8CVE-2024-10542: Spam protection Authorization Bypass
CVE-2024-10542 - 8.1CVE-2024-10781: Spam protection Authorization Bypass
CVE-2024-10781 - 7.5CVE-2021-24295: Spam protection Blind SQL Injection
CVE-2021-24295 - 7.2CVE-2026-77830: Spam protection Stored XSS
CVE-2026-77830 - 7.2CVE-2026-65437: Spam protection Stored XSS
CVE-2026-65437 - 7.2CVE-2026-8071: CleanTalk Anti-Spam. Spam Firewall… Stored XSS
CVE-2026-8071 - 7.2CVE-2022-3302: AntiSpam by CleanTalk <= 5.185 SQL Injection
CVE-2022-3302 - 7.2CVE-2021-24131: Anti-Spam by CleanTalk < 5.149 SQL Injection
CVE-2021-24131
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C