dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-10801

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 arbitrary file uploads due to missing file type validation in the ajax_manage_file_chunk_upload() function in all versions up to, and including, 16.5. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. User registration must be enabled for this to be exploited.

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 versions up to 16.5 lacks file type validation in the ajax_manage_file_chunk_upload() function, allowing unauthenticated attackers to upload arbitrary files to the server when user registration is enabled. This can lead to remote code execution.

MitigationUpdate the plugin to version 16.6 or later immediately. If an update is unavailable, disable user registration and consider removing the plugin until a patch is released. Review the server for any recently uploaded suspicious files.

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

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if WordPress is installed
    Check the site for WordPress indicators such as /wp-admin/ login page, wp-content/ directory, or presence of wp-config.php in the web root
    Affected if Not applicable - this confirms the platform
  2. Verify User Extra Fields plugin is installed and active
    Access wp-admin > Plugins and look for 'User Extra Fields' in the active plugin list, or inspect the plugins directory for 'user-extra-fields' folder
    Affected if Plugin is not installed or not active - not affected
  3. Check the installed plugin version
    In wp-admin > Plugins > User Extra Fields, click on the plugin name to view details and note the version number, or read version from plugin header in wp-content/plugins/user-extra-fields/uef-main.php
    Affected if Version is 16.5 or lower - potentially affected
  4. Confirm user registration is enabled
    In wp-admin > Settings > General, verify the 'Membership' setting shows 'Anyone can register' is checked
    Affected if User registration is enabled - vulnerable configuration present
  5. Check for arbitrary file uploads
    Inspect network traffic during a registration or profile update process that uses file upload, or review wp-content/uploads/ directory for unexpected file types from unauthenticated sources
    Affected if Unexpected file types (php, js, exe) exist in uploads from unknown sources - exploitation may have occurred

User is affected if WordPress with User Extra Fields plugin version 16.5 or lower is installed with user registration enabled, allowing unauthenticated arbitrary file upload.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 16.6 or later immediately. If an update is unavailable, disable user registration and consider removing the plugin until a patch is released. Review the server for any recently uploaded suspicious files.

Recommended fix Moderate confidence

Latest version from wordpress.org (version after 16.5)

  1. 1. Verify if user registration is enabled on the WordPress site; if not enabled, the exploitation vector is not accessible.
  2. 2. Check the current version of the User Extra Fields plugin installed on the site.
  3. 3. Navigate to Plugins > Add New > Upload Plugin or check the plugin's page on wordpress.org for the latest version.
  4. 4. Update the plugin to the latest available version from the official WordPress repository.
  5. 5. If no update is available from the repository, consider disabling the plugin until a patched version is released.
  6. 6. As a further precaution, disable file upload fields in the User Extra Fields plugin settings if file upload functionality is not required.
  7. 7. Review server logs for any suspicious file uploads or unexpected files in the wp-content/uploads/ directory.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10801 — 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-10801 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