dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-52406

CRITICAL · 9.9 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 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 wibergsweb CSV to html csv-to-html allows Upload a Web Shell to a Web Server.This issue affects CSV to html: from n/a through <= 3.26.

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 csv-to-html plugin has an unrestricted file upload vulnerability (CWE-434) that allows attackers to upload executable files (web shells) directly to the web server without proper validation of file type or content. This enables remote code execution by accessing the uploaded malicious file through the web server.

MitigationImplement strict allowlist-based file type validation (checking both magic bytes and MIME type), store uploads outside the web root or disable script execution via .htaccess/nginx config, rename uploaded files, and update to a patched version if available.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 csv-to-html plugin is installed
    Search for plugin files in common locations such as /wp-content/plugins/, /plugins/, or the application's plugin directory. Look for directories or files named 'csv-to-html', 'csv2html', or similar variants.
    Affected if The csv-to-html plugin files are found in the system
  2. Locate the file upload functionality
    Examine the plugin code for file upload forms, endpoints, or handlers. Search for HTML forms with enctype='multipart/form-data', PHP move_uploaded_file() calls, or similar upload mechanisms within the plugin.
    Affected if File upload code or endpoints exist within the csv-to-html plugin
  3. Determine upload directory location
    Inspect the plugin configuration or code to identify the path where uploaded files are stored. Common paths include /uploads/, /files/, /temp/, or directories under the web root.
    Affected if Uploaded files are stored within the web document root (htdocs, public_html, or equivalent)
  4. Check for file type validation
    Review the upload handling code for validation functions that check file extensions, MIME types, or magic bytes. Look for allowlists or denylists of permitted file types.
    Affected if No file type validation exists, or validation can be easily bypassed (e.g., only checks extension)
  5. Inspect upload directory for suspicious files
    List all files in the identified upload directory. Look for file extensions that indicate executable code such as .php, .php5, .phtml, .asp, .aspx, .jsp, .exe, or .sh.
    Affected if Executable or script files (.php, .asp, .jsp, etc.) are present in the upload directory and are web-accessible

You are affected if the csv-to-html plugin is installed and its file upload feature stores files in a web-accessible directory without proper validation of file type or content.

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

Implement strict allowlist-based file type validation (checking both magic bytes and MIME type), store uploads outside the web root or disable script execution via .htaccess/nginx config, rename uploaded files, and update to a patched version if available.

Recommended fix Moderate confidence

csv-to-html version 3.27 or later (the first version after 3.26 that includes the security fix)

  1. 1. Backup the entire website and database before making any changes.
  2. 2. Identify the csv-to-html plugin/theme installation location on the server.
  3. 3. Download the latest version of csv-to-html from the official source (wibergsweb) or WordPress repository.
  4. 4. Replace the existing csv-to-html files with the updated version.
  5. 5. Verify the file permissions are correctly set after upgrade (no execute permissions on uploaded files).
  6. 6. Test file upload functionality to ensure legitimate CSV uploads still work.
  7. 7. Monitor server logs for any suspicious file uploads or web shell attempts.
Caveat Review changelog for any breaking changes between 3.26 and the fixed version; test in staging environment first

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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