CVE-2024-10800

WordPress User Extra Fields <= 16.6 - Missing Authorization to Authenticated (Subscriber+) Privilege Escalation

2024-11-12 00:00
Tonn

Strategic Overview

Status
Patched in 16.7
Affected Plugin
WordPress User Extra Fields
Affected Version
<= 16.6
CVSS
8.8High
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2024-10800
View all WordPress User Extra Fields vulnerabilities

At a glance

CVE-2024-10800 is a high-severity Missing Authorization vulnerability in the WordPress User Extra Fields WordPress plugin, affecting versions <= 16.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 16.7; sites on affected versions should update now. Disclosed November 2024, reported by Tonn.

Vulnerability Overview

The WordPress User Extra Fields plugin for WordPress is vulnerable to privilege escalation due to a missing capability check on the ajax_save_fields() function in all versions up to, and including, 16.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to add custom fields that can be updated and then use the check_and_overwrite_wp_or_woocommerce_fields function to update the wp_capabilities field to have administrator privileges.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-862: Missing Authorization

WordPress User Extra Fields <= 16.6 carries this weakness at ajax_save_fields(), 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 WordPress User Extra Fields the fix is 16.7: builds <= 16.6 are affected, anything from 16.7 onward is not.

Remediation

Update to version 16.7, 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: WordPress User Extra Fields 16.7 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-10800https://www.wordfence.com/threat-intel/vulnerabilities/id/a18fa7e6-813d-4b48-bd4e-5232fb8382d1https://nvd.nist.gov/vuln/detail/CVE-2024-10800

Related records

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