dbcve.org
User Extra FieldsWordPress extension · Vanquish

CVE-2024-10800

HIGH · 8.8 CVSS v3.1 Published 2024-11-13
Fix available
A fix is available. Upgrade to 16.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WordPress User Extra Fields plugin has a privilege escalation vulnerability where the ajax_save_fields() function lacks a capability check, allowing authenticated users with subscriber-level access to modify the wp_capabilities field via the check_and_overwrite_wp_or_woocommerce_fields function and gain administrator privileges.

MitigationUpdate the plugin to version 16.7 or later. If no update is available, disable the plugin and audit user accounts for unauthorized administrator access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
User Extra FieldsWordPress extension
Affected:< 16.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    Navigate to WordPress admin dashboard > Plugins, locate 'User Extra Fields' (or 'Vanquish User Extra Fields'), and note the installed version number. Alternatively, inspect the plugin's main PHP file in wp-content/plugins/user-extra-fields/ or similar path and check the version header comment.
    Affected if The installed version is below 16.7 (e.g., 16.6, 16.5, etc.) or if the version cannot be determined but the plugin is present.
  2. Verify the plugin is active
    In the WordPress Plugins admin page, check whether the User Extra Fields plugin is currently activated. If it is not active, the vulnerable code is not executing.
    Affected if The plugin is active and the version is below 16.7.
  3. Inspect user capabilities for unauthorized admins
    Query the wp_usermeta table (or use a user management plugin/admin users list) and review all users with the 'administrator' role. Cross-reference with known legitimate administrator accounts. Pay particular attention to accounts created recently or with unusual usernames.
    Affected if There are administrator accounts that were created recently or belong to users who should only have subscriber-level access.
  4. Check for modified user roles via the plugin
    If you have database access, query wp_usermeta for meta_key 'wp_capabilities' with meta_value containing 'administrator' and compare against legitimate admin records. Also check access logs for POST requests to admin-ajax.php with action 'save_extrafields' or similar.
    Affected if There are administrator roles assigned to users who previously had only subscriber permissions, or suspicious ajax calls to field-saving endpoints are present in logs.
  5. Audit subscriber-level accounts
    List all users with the 'subscriber' role in WordPress. Verify that these accounts have not had their wp_capabilities meta_value modified to include administrator privileges.
    Affected if Subscriber accounts exist with administrator-level capabilities in the database.

You are affected if the User Extra Fields plugin is installed, active, and running at a version lower than 16.7, or if unauthorized administrator accounts exist in your user database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 16.7 or later
Fixed in 16.7
Interim mitigation

Update the plugin to version 16.7 or later. If no update is available, disable the plugin and audit user accounts for unauthorized administrator access.

Recommended fix High confidence

Version 16.7

  1. 1. Back up your WordPress site database and files before making any changes
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. 3. Find the User Extra Fields plugin in the list
  4. 4. Click 'Update now' if an update is available, or manually upload version 16.7 of the plugin
  5. 5. After updating, verify the plugin version is 16.7 or higher
  6. 6. Confirm that the privilege escalation vulnerability is no longer exploitable by testing that lower-privileged users cannot modify wp_capabilities

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in User Extra Fields Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-10800 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data