CVE-2023-7065

Stop Spammers Security | Block Spam Users, Comments, Forms <= 2024.4 - Cross-Site Request Forgery (CSRF) via sfs_process

2024-05-03 00:00
Lucio Sá

Strategic Overview

Status
Patched in 2024.5
Affected Plugin
Stop Spammers Classic
Affected Version
<= 2024.4
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-7065
View all Stop Spammers Classic vulnerabilities

At a glance

CVE-2023-7065 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Stop Spammers Classic WordPress plugin, affecting versions <= 2024.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2024.5; sites on affected versions should update now. Disclosed May 2024, reported by Lucio Sá.

Vulnerability Overview

The Stop Spammers Security | Block Spam Users, Comments, Forms plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2024.4. This is due to missing or incorrect nonce validation on the sfs_process AJAX action. This makes it possible for unauthenticated attackers to add arbitrary IPs to the plugin's allowlist and blocklist 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 Spammers Classic <= 2024.4 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 2024.5: builds <= 2024.4 are affected, anything from 2024.5 onward is not.

Remediation

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-7065https://www.wordfence.com/threat-intel/vulnerabilities/id/1998cadb-2eb3-4819-aa7c-59e4f777c7f8https://nvd.nist.gov/vuln/detail/CVE-2023-7065

Related records

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