CVE-2025-2935 MEDIUM

CVE-2025-2935: Anti-Spam: Spam Protection | Block Spam Users, Comments, Forms <= 2024.7 - Cross-Site Request Forgery to Multiple Administrative Actions

Vendor Webguyio
Product Stop Spammers Classic
Weakness CWE-352 · CSRF
Published June 6, 2025
Last update April 8, 2026

CVSS base score

5.4/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Stop Spammers Classic versions up to 2024.7 are vulnerable to cross-site request forgery (CSRF) attacks. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires the admin to visit the attacker's page while authenticated. This can lead to unauthorized changes to plugin settings or site configuration.

What an attacker can do

03Attacker Capabilities

Perform unwanted actions on the site by tricking an authenticated admin into visiting a malicious webpage.

Potential impact on your site

04Site Impact

An attacker can modify plugin settings or site configuration if they trick your admin into clicking a malicious link while logged in.

Conditions required to exploit

05Prerequisites

Site admin must be logged in and visit an attacker-controlled webpage; no special privileges or direct site access required.

Key dates

06Disclosure timeline

June 6, 2025 CVE published
April 8, 2026 Record updated