CVE-2025-14795

Stop Spammers Classic <= 2026.1 - Cross-Site Request Forgery via Email Allowlist

2026-01-27 00:00

Strategic Overview

Status: Patched in 2026.2
Affected Plugin: Stop Spammers Classic
Affected Version: <= 2026.1
CVSS: 4.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2025-14795

View all Stop Spammers Classic vulnerabilities

At a glance

CVE-2025-14795 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stop Spammers Classic WordPress plugin, affecting versions <= 2026.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2026.2; sites on affected versions should update now. Disclosed January 2026, reported by JoanClarke2.

Vulnerability Overview

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.

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)

Reaching this weakness in Stop Spammers Classic <= 2026.1 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 2026.2: builds <= 2026.1 are affected, anything from 2026.2 onward is not.

Remediation

Update to version 2026.2, 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 2026.2 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14795 https://www.wordfence.com/threat-intel/vulnerabilities/id/5d6f38d7-a769-422d-ae3f-565cb1cc8a73 https://nvd.nist.gov/vuln/detail/CVE-2025-14795

Related records

Same weakness class

Other vulnerabilities in Stop Spammers Classic

CVSS Vector

4.3

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/