Stop Comment Spam <= 0.5.3 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 0.5.4
- Affected Plugin
- Stop Comment Spam
- Affected Version
<= 0.5.3- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-23826
At a glance
CVE-2025-23826 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stop Comment Spam WordPress plugin, affecting versions <= 0.5.3. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.5.4; sites on affected versions should update now. Disclosed January 2025, reported by SOPROBRO.
Vulnerability Overview
The Stop Comment Spam plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.5.3. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts 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)
Reaching this weakness in Stop Comment Spam <= 0.5.3 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 Comment Spam the fix is 0.5.4: builds <= 0.5.3 are affected, anything from 0.5.4 onward is not.
Remediation
Update to version 0.5.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Stop Comment Spam: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Stop Comment Spam 0.5.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C