User Extra FieldsWordPress extension · Vanquish
CVE-2024-11150
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 · uneditedThe WordPress User Extra Fields plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_tmp_uploaded_file() function in all versions up to, and including, 16.6. This makes it possible for unauthenticated attackers to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php).
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 confidenceThe WordPress User Extra Fields plugin versions up to 16.6 contains an arbitrary file deletion vulnerability in the delete_tmp_uploaded_file() function due to insufficient path validation. Unauthenticated attackers can supply path traversal sequences (e.g., ../../wp-config.php) to delete any file on the server's filesystem, potentially enabling remote code execution by deleting critical WordPress configuration files.
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
< 16.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and versionLocate the plugin directory in wp-content/plugins (typically named 'user-extra-fields', 'uef', or 'vanquish-user-extra-fields') and check the version in the plugin's main PHP file or readme.txt headerAffected if The plugin is installed and the version listed is below 16.7 (e.g., 16.6, 16.5, etc.)
-
Identify the vulnerable delete_tmp_uploaded_file functionSearch the plugin files for the function 'delete_tmp_uploaded_file' - typically found in the main plugin PHP file or an includes/upload fileAffected if The function exists in the plugin code, indicating the vulnerable code path is present
-
Confirm lack of authentication on the vulnerable endpointReview the code around delete_tmp_uploaded_file() to determine if it is hooked to an action accessible to unauthenticated users (check for hooks like wp_ajax_nopriv_, wp_ajax_, or direct function calls without capability checks)Affected if The function can be triggered without authentication - no current_user check or similar authentication guard is present before the file deletion logic
-
Verify path traversal is not sanitizedExamine the delete_tmp_uploaded_file() function code to see if it uses the supplied filename directly in file operations (unlink, delete) without sanitizing '../' sequences or validating the file is within an allowed directoryAffected if The function accepts a filename parameter and passes it directly to a delete operation without validating it stays within an allowed upload temp directory - allowing '../' to traverse and delete arbitrary files
You are affected if the Vanquish User Extra Fields plugin is installed with version 16.6 or below AND the delete_tmp_uploaded_file function is accessible to unauthenticated users without path validation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.7
Update to version 16.7 or later which patches the arbitrary file deletion vulnerability. As a temporary measure, disable the plugin or deploy a WAF rule to block unauthenticated requests to the vulnerable endpoint.
16.7
- Update the User Extra Fields WordPress plugin to version 16.7 or later through the WordPress admin dashboard under Plugins > All Plugins, or replace the plugin files with the 16.7 release.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in User Extra Fields
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-11150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-11150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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