dbcve.org
Wordpress File UploadWordPress extension · Iptanus

CVE-2024-11635

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-08
Fix available
A fix is available. Upgrade to 4.24.15 or later.
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 File Upload plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.24.12 via the 'wfu_ABSPATH' cookie parameter. This makes it possible for unauthenticated attackers to execute code on the server.

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 File Upload plugin versions up to 4.24.12 contains an unauthenticated Remote Code Execution vulnerability. Attackers exploit the 'wfu_ABSPATH' cookie parameter to inject and execute arbitrary code on the server, achieving full system compromise without any authentication credentials.

MitigationImmediately update the WordPress File Upload plugin to version 4.24.13 or later. If patching is not immediately feasible, consider disabling the plugin temporarily or deploying a WAF rule to block requests containing the malicious 'wfu_ABSPATH' cookie parameter.

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
Wordpress File UploadWordPress extension
Affected:< 4.24.15

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. Verify WordPress File Upload plugin is installed
    Check your WordPress site's wp-content/plugins/ directory for the 'wordpress-file-upload' or 'file-upload' folder, or view the installed plugins list in the WordPress admin dashboard.
    Affected if The plugin folder exists in the plugins directory.
  2. Determine installed plugin version
    Open the main plugin file (usually wordpress-file-upload.php) and locate the 'Version' header in the plugin comments, or check the plugin details in WordPress admin under Plugins > Installed Plugins.
    Affected if The reported version is less than 4.24.15 (for example, 4.24.12 or earlier).
  3. Confirm plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to verify the File Upload plugin status is 'Active', or query the wp_options table for the active_plugins option.
    Affected if The plugin is active and serving requests.
  4. Inspect server logs for exploitation attempts
    Review web server access logs (Apache, Nginx, or other) for incoming requests that contain the 'wfu_ABSPATH' cookie parameter. Search for patterns like 'wfu_ABSPATH=' in the logs.
    Affected if Log entries show requests with the wfu_ABSPATH cookie containing suspicious values such as path traversal sequences or PHP code.

Your environment is affected if the WordPress File Upload plugin version is below 4.24.15 and the plugin is currently active on your WordPress site.

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 4.24.15 or later
Fixed in 4.24.15
Interim mitigation

Immediately update the WordPress File Upload plugin to version 4.24.13 or later. If patching is not immediately feasible, consider disabling the plugin temporarily or deploying a WAF rule to block requests containing the malicious 'wfu_ABSPATH' cookie parameter.

Recommended fix High confidence

WordPress File Upload plugin version 4.24.15 or higher

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'WordPress File Upload' plugin
  4. Click 'Update now' or manually update to version 4.24.15 or higher
  5. Verify the plugin is running version 4.24.15 or later after updating

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

Fix this in Wordpress File Upload Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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