CVE-2024-0324

User Profile Builder <= 3.10.8 - Missing Authorization to Plugin Settings Change via wppb_two_factor_authentication_settings_update

2024-01-16 00:00
kodaichodai

Strategic Overview

At a glance

CVE-2024-0324 is a high-severity Improper Access Control vulnerability in the User Profile Builder WordPress plugin, affecting versions <= 3.10.8. It carries a CVSS score of 8.2 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.10.9; sites on affected versions should update now. Disclosed January 2024, reported by kodaichodai.

Vulnerability Overview

The User Profile Builder – Beautiful User Registration Forms, User Profiles & User Role Editor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'wppb_two_factor_authentication_settings_update' function in all versions up to, and including, 3.10.8. This makes it possible for unauthenticated attackers to enable or disable the 2FA functionality present in the Premium version of the plugin for arbitrary user roles.

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, and no interaction from a victim user. A successful exploit has high impact on integrity.

CWE-284: Improper Access Control

User Profile Builder <= 3.10.8 carries this weakness at wppb_two_factor_authentication_settings_update, and reaching it takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For User Profile Builder the fix is 3.10.9: builds <= 3.10.8 are affected, anything from 3.10.9 onward is not.

Remediation

Update to version 3.10.9, 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.9 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