dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-51919

CRITICAL · 9.0 CVSS v3.1 Published 2025-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
99/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 radykal Fancy Product Designer fancy-product-designer.This issue affects Fancy Product Designer: from n/a through <= 6.4.3.

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 Fancy Product Designer WordPress plugin allows unrestricted file uploads without proper validation of file types, enabling attackers to upload dangerous file types (such as executable PHP scripts) directly to the web server. This could allow remote code execution.

MitigationRestrict file uploads to safe, non-executable types only (e.g., images, PDFs) and validate both file extension and content/MIME type. Store uploads outside the web root or rename files to prevent direct execution.

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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. Confirm Fancy Product Designer plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Fancy Product Designer' or check wp-content/plugins/ directory for the fancy-product-designer folder
    Affected if The plugin is not installed
  2. Identify the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find Fancy Product Designer, and note the version number displayed
    Affected if The version is within the affected range (prior to the patched version)
  3. Verify file upload functionality is accessible
    Navigate to the plugin settings or any product design interface where file uploads are permitted; check if the upload endpoint responds at /wp-content/plugins/fancy-product-designer/
    Affected if The file upload feature is active and accessible to users
  4. Test upload directory configuration
    Check wp-content/uploads/fancy-product-designer/ or similar upload directories; verify if files are stored within the web root and retain their original extensions
    Affected if Uploads are stored in accessible web directories with unchanged file extensions
  5. Review uploaded file type restrictions
    Attempt to upload a test file with a .php extension or inspect the plugin code for file type validation in includes/class-file-upload.php or similar upload handling files
    Affected if The plugin accepts executable file types without proper validation

You are affected if Fancy Product Designer is installed with an unpatched version and the file upload feature is active, allowing potentially malicious files to be stored within the web root.

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

Restrict file uploads to safe, non-executable types only (e.g., images, PDFs) and validate both file extension and content/MIME type. Store uploads outside the web root or rename files to prevent direct execution.

Recommended fix High confidence

Upgrade to Fancy Product Designer version 6.4.4 or later (the first version containing the security fix)

  1. 1. Backup your current Fancy Product Designer installation and database before making any changes.
  2. 2. Identify your current Fancy Product Designer version by checking the plugin files or WordPress admin panel.
  3. 3. Navigate to the WordPress admin dashboard > Plugins > Fancy Product Designer.
  4. 4. If an update is available, click to update to the latest version.
  5. 5. Verify the update was successful and the version is above 6.4.3.
  6. 6. Test the file upload functionality to ensure the plugin still works correctly after the update.
  7. 7. Monitor the website for any unusual behavior following the update.
Caveat Review plugin settings and custom integrations after upgrade as minor functionality changes may occur between versions

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