CVE-2023-6504

Profile Builder <= 3.10.7 - Insecure Direct Object Reference to Sensitive Information Exposure via user_meta Shortcode

2024-01-05 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 3.10.8
Affected Version
<= 3.10.6
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-6504
View all User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor vulnerabilities

At a glance

CVE-2023-6504 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the User Profile Builder WordPress plugin, affecting versions <= 3.10.6. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 3.10.8; sites on affected versions should update now. Disclosed January 2024, reported by Francesco Carlucci.

Vulnerability Overview

The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the wppb_toolbox_usermeta_handler function in all versions up to, and including, 3.10.7. This makes it possible for authenticated attackers, with contributor-level access and above, to expose sensitive information within user metadata.

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 User Profile Builder <= 3.10.6 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 User Profile Builder the fix is 3.10.8: builds <= 3.10.6 are affected, anything from 3.10.8 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

Related records

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