CVE-2024-10537

WP User Manager – User Profile Builder & Membership <= 2.9.11 - Missing Authorization to Authenticated (Subscriber+) User Meta Key Enumeration

2024-11-22 00:00
Tieu Pham Trong Nhan

Strategic Overview

Status
Patched in 2.9.12
Affected Version
<= 2.9.11
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10537
View all WP User Manager – User Profile Builder & Membership vulnerabilities

At a glance

CVE-2024-10537 is a medium-severity Missing Authorization vulnerability in the WP User Manager WordPress plugin, affecting versions <= 2.9.11. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.9.12; sites on affected versions should update now. Disclosed November 2024, reported by Tieu Pham Trong Nhan.

Vulnerability Overview

The WP User Manager – User Profile Builder & Membership plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the validate_user_meta_key() function in all versions up to, and including, 2.9.11. This makes it possible for authenticated attackers, with Subscriber-level access and above, to enumerate user meta keys.

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-862: Missing Authorization

WP User Manager <= 2.9.11 carries this weakness at validate_user_meta_key(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP User Manager the fix is 2.9.12: builds <= 2.9.11 are affected, anything from 2.9.12 onward is not.

Remediation

Update to version 2.9.12, 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 User Manager 2.9.12 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