Skip to content

Product

wordpress cleantalk-spam-protect vulnerabilities

20 published CVES affecting wordpress cleantalk-spam-protect, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
20
Critical
1
High
13
Medium
6
Low
0
Unscored
0
CISA KEV
0

Latest wordpress cleantalk-spam-protect CVEs

Newest publication first

  1. CriticalCVSS 9.8 EPSS 1.3%

    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....

  2. HighCVSS 7.5 EPSS 13.2%

    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 make...

  3. HighCVSS 7.5 EPSS 3.2%

    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 po...

  4. HighCVSS 7.2 EPSS 1.4%

    The Spam protection, AntiSpam, FireWall by CleanTalk WordPress plugin before 5.185.1 does not validate ids before using them in a SQL statement, which could lead to SQL injection exploitable by high privilege users such as admin

  5. MediumCVSS 6.1 EPSS 2.9%

    The CleanTalk AntiSpam plugin <= 5.173 for WordPress is vulnerable to Reflected Cross-Site Scripting (XSS) via the $_REQUEST['page'] parameter in/lib/Cleantalk/ApbctWP/FindSpam/ListTable/Users.php

  6. MediumCVSS 6.1 EPSS 2.4%

    The CleanTalk AntiSpam plugin <= 5.173 for WordPress is vulnerable to Reflected Cross-Site Scripting (XSS) via the $_REQUEST['page'] parameter in/lib/Cleantalk/ApbctWP/FindSpam/ListTable/Comments.php

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.