CVE-2024-3983

WooCommerce Customers Manager < 30.1 - Cross-Site Request Forgery to Customer Deletion

2024-07-11 00:00
Bob Matyas

Strategic Overview

Status
Patched in 30.1
Affected Version
< 30.1
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-3983
View all WooCommerce Customers Manager vulnerabilities

At a glance

CVE-2024-3983 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WooCommerce Customers Manager WordPress plugin, affecting versions < 30.1. 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 30.1; sites on affected versions should update now. Disclosed July 2024, reported by Bob Matyas.

Vulnerability Overview

The WooCommerce Customers Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 30.1 (exclusive). This is due to missing or incorrect nonce validation on the 'woocommerce-customers-manager' page. This makes it possible for unauthenticated attackers to delete customers 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)

WooCommerce Customers Manager < 30.1 carries this weakness at woocommerce-customers-manager, and reaching it 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 WooCommerce Customers Manager the fix is 30.1: builds < 30.1 are affected, anything from 30.1 onward is not.

Remediation

Update to version 30.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WooCommerce Customers Manager: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WooCommerce Customers Manager 30.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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