CVE-2025-9979

Maspik <= 2.5.6 - Authenticated (Subscriber+) Missing Authorization to Spam Log Export

2025-09-09 17:27
Dmitrii Ignatyev

Strategic Overview

Status
Patched in 2.5.7
Affected Plugin
Spam Protection | Maspik
Affected Version
<= 2.5.6
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-9979
View all Spam Protection | Maspik vulnerabilities

At a glance

CVE-2025-9979 is a medium-severity Missing Authorization 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 an authenticated account at Subscriber level or above. 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 plugin for WordPress is vulnerable to Missing Authorization in version 2.5.6 and prior. This is due to missing capability checks on the Maspik_spamlog_download_csv function. This makes it possible for authenticated attackers, with subscriber-level access and above, to export and download the spam log database containing blocked submission attempts, which may include misclassified but legitimate submissions with sensitive data.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Spam Protection <= 2.5.6 takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. 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?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Spam Protection 2.5.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-9979https://www.wordfence.com/threat-intel/vulnerabilities/id/7ee68705-cbb3-44b8-8223-4cecd678bcabhttps://nvd.nist.gov/vuln/detail/CVE-2025-9979

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C