dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-49291

CRITICAL · 10.0 CVSS v3.1 Published 2024-10-17
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 Gora Tech LLC Cooked Pro.This issue affects Cooked Pro: from n/a before 1.8.0.

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

Unrestricted file upload vulnerability in Cooked Pro WordPress plugin allows attackers to upload dangerous file types (e.g., executable scripts, PHP files) before version 1.8.0, potentially leading to remote code execution on the server.

MitigationUpgrade Cooked Pro to version 1.8.0 or later. If immediate patching is not possible, disable the file upload functionality or restrict file uploads at the web server level (e.g., via .htaccess or nginx configuration) until the update 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
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. Verify Cooked Pro plugin is installed
    Check the WordPress plugins directory or navigate to Plugins > Installed Plugins in the WordPress admin dashboard to confirm Cooked Pro is present
    Affected if Cooked Pro plugin is found installed
  2. Determine installed Cooked Pro version
    Access the plugin details page in WordPress admin (Plugins > Installed Plugins > Cooked Pro) or inspect the main plugin file header for the version number
    Affected if Version is below 1.8.0 or cannot be determined against the affected range
  3. Confirm file upload functionality is enabled
    Review Cooked Pro plugin settings pages in the WordPress admin dashboard to identify if file upload or recipe media upload features are active
    Affected if File upload functionality is enabled in the plugin configuration

Environment is affected if Cooked Pro plugin is installed with a version below 1.8.0 and the file upload feature is enabled.

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

Upgrade Cooked Pro to version 1.8.0 or later. If immediate patching is not possible, disable the file upload functionality or restrict file uploads at the web server level (e.g., via .htaccess or nginx configuration) until the update can be applied.

Recommended fix Moderate confidence

1.8.0

  1. Backup your WordPress site and database before performing any updates
  2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard
  3. Deactivate the current version of Cooked Pro
  4. Delete the existing Cooked Pro plugin files
  5. Install Cooked Pro version 1.8.0 or later from the WordPress plugin repository or your trusted source
  6. Activate the new version of Cooked Pro
  7. Verify the plugin functionality and ensure the upload feature works correctly after the upgrade

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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