dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-52373

CRITICAL · 10.0 CVSS v3.1 Published 2024-11-14
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
Unrestricted Upload of File with Dangerous Type vulnerability in Team Devexhub Devexhub Gallery devexhub-gallery allows Upload a Web Shell to a Web Server.This issue affects Devexhub Gallery: from n/a through <= 2.0.1.

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 Devexhub Gallery plugin for WordPress suffers from an unrestricted file upload vulnerability (CWE-434) that allows unauthenticated attackers to upload arbitrary files, including PHP web shells, directly to the web server. This leads to complete remote code execution on the affected system.

MitigationImplement strict allowlist-based file type validation (MIME type, extension, and file content/magic bytes validation) for all uploaded files, store uploads outside the web root, disable script execution in the upload directory, and remove any uploaded files that contain executable code.

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 Devexhub Gallery plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Devexhub Gallery' in the list, or check the /wp-content/plugins/ directory for a folder named 'devexhub-gallery' or similar
    Affected if The Devexhub Gallery plugin appears in the installed plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, click on the Devexhub Gallery plugin to view its version number, or inspect the main plugin PHP file for a version constant or header
    Affected if The installed version is unknown, unpatched, or falls within any vulnerable version range
  3. Inspect the plugin upload directory
    Check the uploads folder (typically /wp-content/uploads/) for any directories created by the Devexhub Gallery plugin, then list all files in those directories to identify unexpected file types
    Affected if The plugin creates an accessible upload directory containing files with executable extensions (php, phtml, js) or unrecognized file types
  4. Search for recently created PHP files in web root
    Use command line (e.g., 'find /var/www -name "*.php" -mtime -30') or file explorer to locate PHP files created within the last 30 days, especially in upload directories or the plugin folder itself
    Affected if PHP files exist that were not intentionally placed there by administrators, particularly in upload directories
  5. Review web server access logs for upload POST requests
    Examine web server logs (Apache access.log, Nginx access.log) for POST requests to the Devexhub Gallery upload endpoint, looking for unusual file extensions or repeated upload attempts
    Affected if Logs show unauthenticated POST requests uploading files to the plugin's upload functionality, especially with extensions like .php or .phtml

A user is affected if the Devexhub Gallery plugin is installed and its upload functionality is exposed to unauthenticated requests, or if unauthorized executable files exist in the upload directories.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based file type validation (MIME type, extension, and file content/magic bytes validation) for all uploaded files, store uploads outside the web root, disable script execution in the upload directory, and remove any uploaded files that contain executable code.

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-52373 — 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-52373 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