Anti-Spam: Spam Protection | Block Spam Users, Comments, Forms <= 2024.7 - Cross-Site Request Forgery to Multiple Administrative Actions
Strategic Overview
- Status
- Patched in 2025
- Affected Plugin
- Stop Spammers Classic
- Affected Version
<= 2024.7- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-2935
At a glance
CVE-2025-2935 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stop Spammers Classic WordPress plugin, affecting versions <= 2024.7. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2025; sites on affected versions should update now. Disclosed June 2025, reported by Noah Stead (TurtleBurg).
Vulnerability Overview
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.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Stop Spammers Classic <= 2024.7 carries this weakness at and, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Stop Spammers Classic the fix is 2025: builds <= 2024.7 are affected, anything from 2025 onward is not.
Remediation
Update to version 2025, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Stop Spammers Classic: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Stop Spammers Classic 2025 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Stop Spammers Classic
- 9.8CVE-2022-4120: Stop Spammers Security <= 2022.5 PHP Object Injection
CVE-2022-4120 - 7.2CVE-2026-48876: Stop Spammers Classic <= 2026.3 Stored XSS
CVE-2026-48876 - 6.1CVE-2023-2488: Stop Spammers Security <= 2022.6 Reflected XSS
CVE-2023-2488 - 6.1CVE-2021-24245: Stop Spammers <= 2021.8 Reflected Cross-Site Scripting
CVE-2021-24245 - 4.8CVE-2021-24517: Stop Spammers Security <= 2021.17 Stored XSS
CVE-2021-24517 - 4.4CVE-2023-2489: Stop Spammers Security <= 2022.6 Stored XSS
CVE-2023-2489
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C