CVE-2023-24008

Maspik – Spam blacklist <= 0.7.8 - Cross-Site Request Forgery

2023-02-27 00:00
Kévin Mosbahi (Mika)

Strategic Overview

Status
Patched in 0.7.9
Affected Plugin
Spam Protection | Maspik
Affected Version
<= 0.7.8
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-24008
View all Spam Protection | Maspik vulnerabilities

At a glance

CVE-2023-24008 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Spam Protection WordPress plugin, affecting versions <= 0.7.8. 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 0.7.9; sites on affected versions should update now. Disclosed February 2023, reported by Kévin Mosbahi (Mika).

Vulnerability Overview

The Maspik plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 0.7.8. This is due to missing or incorrect nonce validation in the file /admin/partials/contact-forms-anti-spam-log.php. This makes it possible for unauthenticated attackers to clear plugin logs and stat counter 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 <= 0.7.8 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 0.7.9: builds <= 0.7.8 are affected, anything from 0.7.9 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-24008https://www.wordfence.com/threat-intel/vulnerabilities/id/0206aead-d146-453d-99ed-3870f7dfdae9https://nvd.nist.gov/vuln/detail/CVE-2023-24008

Related records

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