CVE-2025-11755

Delicious Recipes <= 1.9.0 - Authenticated (Contributor+) Arbitrary File Upload

2025-10-31 18:07
stealthcopter

Strategic Overview

Status
Patched in 1.9.1
Affected Version
<= 1.9.0
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2025-11755
View all WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) vulnerabilities

At a glance

CVE-2025-11755 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WP Delicious WordPress plugin, affecting versions <= 1.9.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.9.1; sites on affected versions should update now. Disclosed October 2025, reported by stealthcopter.

Vulnerability Overview

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 Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in WP Delicious <= 1.9.0 takes an account at Contributor level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For WP Delicious the fix is 1.9.1: builds <= 1.9.0 are affected, anything from 1.9.1 onward is not.

Remediation

Update to version 1.9.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP Delicious 1.9.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C