CVE-2024-12436

WP Customer Area <= 8.2.4 - Cross-Site Request Forgery to Bulk Deletion

2025-01-06 00:00
Bob Matyas

Strategic Overview

Status
Patched in 8.2.5
Affected Plugin
WP Customer Area
Affected Version
<= 8.2.4
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-12436
View all WP Customer Area vulnerabilities

At a glance

CVE-2024-12436 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Customer Area WordPress plugin, affecting versions <= 8.2.4. 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 8.2.5; sites on affected versions should update now. Disclosed January 2025, reported by Bob Matyas.

Vulnerability Overview

The WP Customer Area plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 8.2.4. This is due to missing or incorrect nonce validation on the 'cuar-trash' action. This makes it possible for unauthenticated attackers to delete customer files 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)

WP Customer Area <= 8.2.4 carries this weakness at cuar-trash, 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 WP Customer Area the fix is 8.2.5: builds <= 8.2.4 are affected, anything from 8.2.5 onward is not.

Remediation

Update to version 8.2.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Customer Area: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Customer Area 8.2.5 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