Strategic Overview
- Status
- Patched in 2.5.7
- Affected Plugin
- Spam Protection | Maspik
- Affected Version
<= 2.5.6- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-9888
At a glance
CVE-2025-9888 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Spam Protection WordPress plugin, affecting versions <= 2.5.6. 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 2.5.7; sites on affected versions should update now. Disclosed September 2025, reported by Dmitrii Ignatyev.
Vulnerability Overview
The Maspik – Ultimate Spam Protection plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.5.6. This is due to missing or incorrect nonce validation on the clear_log function. This makes it possible for unauthenticated attackers to clear all spam logs 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 Spam Protection <= 2.5.6 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 Spam Protection the fix is 2.5.7: builds <= 2.5.6 are affected, anything from 2.5.7 onward is not.
Remediation
Update to version 2.5.7, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Spam Protection: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Spam Protection 2.5.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Spam Protection | Maspik
- 7.2CVE-2026-28003: Maspik – Spam blacklist <= 2.9.1 Stored XSS
CVE-2026-28003 - 6.1CVE-2023-48272: Maspik – Spam blacklist <= 0.9.2 Stored XSS
CVE-2023-48272 - 5.3CVE-2023-48271: Maspik – Spam blacklist <= 0.10.3 Bypass
CVE-2023-48271 - 4.4CVE-2024-9182: Maspik – Spam blacklist <= 2.1.2 Stored XSS
CVE-2024-9182 - 4.4CVE-2024-25101: Maspik – Spam blacklist <= 0.10.6 Stored XSS
CVE-2024-25101 - 4.3CVE-2025-9979: Maspik <= 2.5.6 Spam Log Export
CVE-2025-9979
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C