dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-52416

CRITICAL · 10.0 CVSS v3.1 Published 2024-11-16
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
Missing Authorization vulnerability in Eugen Bobrowski Debug Tool debug-tool allows Upload a Web Shell to a Web Server.This issue affects Debug Tool: from n/a through <= 2.2.

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 · moderate confidence

The Debug Tool plugin by Eugen Bobrowski lacks proper authorization checks on its upload functionality, allowing unauthenticated attackers to upload arbitrary files including web shells directly to the web server.

MitigationImmediately remove or disable the debug tool from production environments. If the tool is required, implement proper authentication and authorization controls before any file upload operations are permitted.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 Debug Tool plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'debug-tool' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for a plugin authored by Eugen Bobrowski or named Debug Tool.
    Affected if The Debug Tool plugin by Eugen Bobrowski is found installed on the WordPress site.
  2. Check the installed plugin version
    In WordPress admin, find Debug Tool in the plugins list and note the version number displayed. Alternatively, open the main plugin file (debug-tool.php or similar) and look for the 'Version' header in the plugin comment block.
    Affected if The installed version is unknown, unpatched, or lower than any fixed version released after CVE-2024-52416.
  3. Verify if upload functionality is exposed without authentication
    Attempt to access the plugin's upload endpoint directly (commonly at /wp-content/plugins/debug-tool/upload.php or similar path). Use a tool like curl to send a request without any authentication cookies or credentials. Check if the endpoint accepts requests and returns a successful response.
    Affected if The upload functionality responds to unauthenticated requests with any success or upload-accepted status (not a 401/403 redirect to login).
  4. Inspect uploads directory for suspicious files
    Examine the wp-content/uploads/ directory (and any subdirectories) for unfamiliar PHP files, shell scripts, or files with double extensions (e.g., shell.php.jpg). Use file system search: find wp-content/uploads/ -name '*.php' -o -name '*.php*'
    Affected if Any PHP files or web shells are found in the uploads directory that were not intentionally uploaded by an administrator.

You are affected if the Debug Tool plugin by Eugen Bobrowski is installed AND its upload endpoint accepts unauthenticated requests, or if unexpected PHP files exist in the uploads directory.

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

Immediately remove or disable the debug tool from production environments. If the tool is required, implement proper authentication and authorization controls before any file upload operations are permitted.

Recommended fix Moderate confidence

Latest version available from vendor (version > 2.2)

  1. 1. Identify all deployments of the Debug Tool plugin/theme by Eugen Bobrowski version 2.2 or earlier
  2. 2. Check the official source (WordPress plugin repository or vendor distribution channel) for the latest available version
  3. 3. Upgrade Debug Tool to the latest version available from the vendor (version higher than 2.2)
  4. 4. Verify the upgrade completed successfully
  5. 5. Confirm the debug tool functionality still works as expected post-upgrade
  6. 6. Review server for any unauthorized files that may have been uploaded during any potential exploitation

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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