CVE-2023-6741

WP Customer Area <= 8.2.1 - Insecure Direct Object Reference to Address Modification

2024-01-10 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 8.2.1
Affected Plugin
WP Customer Area
Affected Version
<= 8.2.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-6741
View all WP Customer Area vulnerabilities

At a glance

CVE-2023-6741 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Customer Area WordPress plugin, affecting versions <= 8.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 8.2.1; sites on affected versions should update now. Disclosed January 2024, reported by Krzysztof Zając.

Vulnerability Overview

The WP Customer Area plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the save_address_for_owner function in all versions up to, and including, 8.2.0. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify addresses for other owners.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP Customer Area <= 8.2.0 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP Customer Area the fix is 8.2.1: builds <= 8.2.0 are affected, anything from 8.2.1 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6741https://www.wordfence.com/threat-intel/vulnerabilities/id/32713069-ea40-46ef-a789-9646eab2e651https://nvd.nist.gov/vuln/detail/CVE-2023-6741

Related records

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