dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2025-11755

HIGH · 8.8 CVSS v3.1 Published 2025-11-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/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
The WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) plugin for WordPress is vulnerable to arbitrary file uploads when importing recipes via CSV in all versions up to, and including, 1.9.0. This flaw allows an attacker with at least Contributor-level permissions to upload a malicious PHP file by providing a remote URL during a recipe import process, leading to Remote Code Execution (RCE).

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 WP Delicious WordPress plugin up to version 1.9.0 allows arbitrary file uploads through its CSV recipe import feature. Attackers with Contributor-level permissions can supply a remote URL pointing to a malicious PHP file during import, which gets uploaded and executed on the server, achieving Remote Code Execution.

MitigationUpdate the WP Delicious plugin to a version beyond 1.9.0, or disable/restrict the CSV import functionality until a patch is applied. Review user role permissions as a defense-in-depth measure.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 WP Delicious plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and locate 'WP Delicious' (also known as Delicious Recipes). Note the version number displayed.
    Affected if Plugin is installed with version 1.9.0 or lower
  2. Confirm affected version range
    Compare the installed version to the affected range (1.9.0 and below). The plugin version is typically shown next to the plugin name on the Plugins page.
    Affected if Version is 1.9.0 or any version up to 1.9.0
  3. Check for CSV recipe import feature
    Look for a recipe import option within the plugin settings. In WordPress admin, navigate to Recipes or the plugin's settings menu and look for 'Import' or 'CSV Import' functionality.
    Affected if CSV import feature is present and accessible to Contributor-level users or higher
  4. Inspect upload directories for suspicious PHP files
    Check the wp-content/uploads directory (or custom upload path) for unexpected .php files, especially in recent date-based subfolders. Use file manager or command line: find /path/to/wp-content/uploads -name "*.php" -mtime -7
    Affected if Unexpected PHP files exist in upload directories, particularly if recently created

A user is affected if they have WP Delicious plugin version 1.9.0 or lower installed with the CSV import feature enabled and accessible to users with Contributor permissions or higher.

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

Update the WP Delicious plugin to a version beyond 1.9.0, or disable/restrict the CSV import functionality until a patch is applied. Review user role permissions as a defense-in-depth measure.

Recommended fix Moderate confidence

Version 1.9.1 or later (upgrade to latest available version)

  1. 1. Log in to WordPress admin dashboard with Administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'WP Delicious – Recipe Plugin for Food Bloggers' (or 'Delicious Recipes')
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/delicious-recipes/ and upload manually via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the version number reflects the fix (version 1.9.1 or higher)
  7. 7. Test the recipe import functionality to confirm it still works correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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