HomeWordPress vulnerabilitiesStop Spammers Classic
Stop Spammers Classic vulnerabilities
Stop Spammers Classic has 2 known vulnerabilities in this database. The most recent published record is dated 28 Jan 2026.
- Known vulnerabilities
- 2
- Active installs
- 20,000+
- Latest version
- 2026.6
- Last updated
- 18 Jul 2026
- Most recent
- 28 Jan 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 request forgery (CSRF) CVE-2025-14795 | Medium 4.3 | Up to 2026.1 | Fixed in a later version (latest 2026.6) | 28 Jan 2026 |
| Cross-site request forgery (CSRF) CVE-2025-2935 | Medium 5.4 | Up to 2024.7 | Fixed in a later version (latest 2026.6) | 6 Jun 2025 |
Read the published descriptions
- CVE-2025-14795, 28 Jan 2026
- The Stop Spammers Classic plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2026.1. This is due to missing nonce validation in the ss_addtoallowlist class. This makes it possible for unauthenticated attackers to add arbitrary email addresses to the spam allowlist via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. The vulnerability was partially patched in version 2026.1. CVE record
- CVE-2025-2935, 6 Jun 2025
- The Anti-Spam: Spam Protection | Block Spam Users, Comments, Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2024.7. This is due to missing or incorrect nonce validation in the 'ss_option_maint.php' and 'ss_user_filter_list' files. This makes it possible for unauthenticated attackers to delete pending comments, and re-enable a previously blocked user via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
What to do if you run Stop Spammers Classic
If you run Stop Spammers Classic, 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 Stop Spammers Classic vulnerabilities
Free. We email you when a new vulnerability is published for Stop Spammers Classic, 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.