dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-10590

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Opt-In Downloads plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the admin_upload() function in all versions up to, and including, 4.07. This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible. Due to the presence of an .htaccess file, this can only be exploited to achieve RCE on NGINX servers, unless another vulnerability is present.

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 Opt-In Downloads WordPress plugin lacks file type validation in its admin_upload() function, allowing authenticated users with Subscriber-level permissions to upload arbitrary files. While an .htaccess provides partial protection on Apache, NGINX deployments are fully vulnerable to remote code execution.

MitigationUpdate to patched version when available, or add proper file type validation and extension checking in admin_upload(); temporarily restrict upload permissions to Administrator-level users until patched.

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
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. Verify Opt-In Downloads plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Opt-In Downloads' in the installed plugins list, or check the filesystem under wp-content/plugins for a folder named 'opt-in-downloads' or similar
    Affected if Plugin is installed and active
  2. Determine the web server software
    Check the server response headers for 'Server: nginx' or run 'nginx -v' on the host, or inspect the web server configuration files
    Affected if Server is NGINX (lacks .htaccess protection that Apache has)
  3. Check if Subscriber role has upload access
    Navigate to WordPress admin > Users > Roles, or inspect wp_capabilities in wp_usermeta for a Subscriber user, or check if the plugin creates any custom roles with upload permissions
    Affected if Subscriber-level accounts exist and can access upload functionality
  4. Inspect the admin_upload function for file type validation
    Examine the plugin source code files (likely in includes/admin-upload.php or similar) and look for validation functions like wp_check_filetype, mime type checking, or extension whitelist logic before file processing
    Affected if No file type or extension validation is present before the upload handling code
  5. Test for unauthenticated or low-privilege upload capability
    Using a Subscriber-level account, attempt to access the upload endpoint (usually wp-admin/admin-ajax.php?action=opt_in_downloads_upload or similar path defined by the plugin) and submit a file with a non-standard extension like .php
    Affected if Upload completes without error or restriction for Subscriber users

User is affected if the Opt-In Downloads plugin is installed on a NGINX server with Subscriber-level users having access to an upload function that lacks file type validation.

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 to patched version when available, or add proper file type validation and extension checking in admin_upload(); temporarily restrict upload permissions to Administrator-level users until patched.

Recommended fix Moderate confidence

Opt-In Downloads plugin version 4.08 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Opt-In Downloads' plugin
  4. Check the current version installed (should be 4.07 or earlier)
  5. Update the plugin to the latest available version (4.08 or higher)
  6. Verify the update was successful and the plugin is functioning correctly
  7. Consider restricting file upload permissions for Subscriber-level users until the patch is applied

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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