dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-10586

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 Debug Tool plugin for WordPress is vulnerable to arbitrary file creation due to a missing capability check on the dbt_pull_image() function and missing file type validation in all versions up to, and including, 2.2. This makes it possible for unauthenticated attackers to to create arbitrary files such as .php files that can be leveraged for remote code execution. CVE-2024-52416 may be a duplicate of this issue.

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 Debug Tool plugin for WordPress contains an unauthenticated arbitrary file creation vulnerability in versions up to 2.2. The dbt_pull_image() function lacks both capability checks (authorization) and file type validation, allowing remote attackers to write arbitrary files including PHP scripts to the server, leading to remote code execution.

MitigationUpdate the Debug Tool plugin to version 2.3 or later. If no update is available, disable the plugin immediately. Consider implementing web application firewall rules to block requests to the vulnerable endpoint until the patch can be applied.

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. Verify Debug Tool plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'debug-tool' or similar.
    Affected if The Debug Tool plugin appears in the installed plugins list.
  2. Check installed plugin version
    In the Plugins list within WordPress admin, click on the Debug Tool plugin to view its details, or read the main plugin PHP file (usually debug-tool.php or similar) and look for the version defined in the plugin header comment.
    Affected if The reported version is 2.2 or lower.
  3. Confirm plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify the Debug Tool plugin status shows as 'Active'.
    Affected if The plugin is active and running.
  4. Inspect for unauthorized files
    Review the WordPress uploads directory (typically /wp-content/uploads/) and the plugin directory (/wp-content/plugins/debug-tool/) for any unfamiliar PHP files or scripts that were not intentionally uploaded.
    Affected if Unexpected PHP files are present in these directories.

A user is affected if the Debug Tool plugin versions 2.2 or lower are installed and active on their WordPress site, as the vulnerable dbt_pull_image() function can be exploited without authentication to create arbitrary files.

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 Debug Tool plugin to version 2.3 or later. If no update is available, disable the plugin immediately. Consider implementing web application firewall rules to block requests to the vulnerable endpoint until the patch can be applied.

Recommended fix Moderate confidence

Latest version of Debug Tool plugin (version higher than 2.2)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'Debug Tool' plugin
  4. Check if the currently installed version is 2.2 or earlier
  5. If vulnerable, click 'Update Now' to install the latest version
  6. Alternatively, download the latest version from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the new version number reflects the update
  8. Confirm the dbt_pull_image() function is no longer accessible to unauthenticated users

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
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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