Skip to main content

WP Delicious EUVDEUVD-2026-87535

| CVE-2026-92411 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-26 WPScan GHSA-9j5m-mgr6-gp3g
6.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain Contributor-level account
  2. Delivery
    Inject script into recipe block HTML tag name
  3. Exploit
    Payload stored unescaped in recipe
  4. Execution
    Admin/visitor views recipe page
  5. Impact
    Script executes in victim browser session

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated account with the Contributor role or higher on the target WordPress site running WP Delicious before 1.10.8; the attacker must be able to create/edit a recipe block (the plugin's core feature). Exploitation depends on the unvalidated HTML tag name field in user-supplied recipe block data. Payload execution requires victim interaction (UI:R) - an administrator or visitor must view the published recipe page. Limiting factors: the contributor authentication barrier means this is not remotely exploitable against anonymous users, and sites that restrict recipe authorship to trusted users face lower practical risk; stored payloads on public recipe pages, however, will hit any casual visitor.

Impact

This is a stored/persistent Cross-Site Scripting flaw (CWE-79) in the WP Delicious recipe plugin, rated by the vendor at CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H). The signals point to a moderate, not urgent, priority. EPSS is very low at 0.15% (4th percentile), there is no CISA KEV listing, and the SSVC framework returns Exploitation: none and Automatable: no - indicating no observed exploitation and that this is not mass-scannable/wormable (it requires an authenticated contributor account). Countering this, a public POC exists via WPScan and SSVC rates Technical Impact as 'total', reflecting that arbitrary script execution in the admin/visitor browser context can fully compromise the affected session. Note two conflicts in the supplied vector: the description states 'Contributor role and above,' which is a LOW-privilege authenticated role and better maps to PR:L, yet the vendor vector uses PR:H - the vendor OVERSTATES the access barrier. Simultaneously the C:H/I:H/A:H impact metrics are INFLATED for a same-scope stored XSS, which normally yields limited C/I and no A. Net effect: this is a real but bounded issue gated behind an authenticated contributor account, best treated as medium priority - patch promptly but it is not a drop-everything emergency.

Exploit ScenarioDerived

An attacker who holds (or phishes/registers into) a Contributor account on a WP Delicious site edits a recipe block and injects a malicious HTML tag name containing a script payload, which is stored unescaped. When an administrator or ordinary visitor later views the published recipe page, the script executes in their browser under the site's origin, enabling session/cookie theft or admin actions via the victim's authenticated session. A public POC is available from WPScan, lowering the effort to reproduce.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 27, 2026

WP Delicious versions before 1.10.8 are affected by a stored cross-site scripting flaw that lets Contributor-level and higher accounts inject arbitrary HTML, including script tags, through unescaped HTML tag names in recipe block data, with execution occurring when a victim views the recipe page. Publicly available exploit code exists, the vendor has released a patch in version 1.10.8, and EPSS is low at 0.15% (4th percentile); no KEV listing or active exploitation has been confirmed.

RemediationAI

Upgrade WP Delicious to version 1.10.8 or later; this is the vendor-released patch and the primary remediation. Because publicly available exploit code exists, prioritize the update on any site allowing Contributor-level users to create or edit recipes. If immediate patching is not possible, temporarily restrict recipe creation and editing to Administrator accounts only (side effect: reduces content workflow but closes the Contributor attack path), or disable the recipe block feature until the update can be applied. Review existing recipe content for injected tags and remove any suspicious script elements. Refer to the vendor advisory at https://wpscan.com/vulnerability/f76a4694-8073-41fe-bb49-4073e6e95ac3/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-92411 for details. A web application firewall rule blocking script tags in recipe fields can serve as a temporary compensating control, though it may not catch all obfuscated payloads.

Affected VersionsENISA

WP Delicious 0 <1.10.8

Affected Packages

euvd wp_delicious fix: 1.10.8

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., cross-site scripting). WP Delicious is a WordPress recipe plugin whose recipe blocks accept user-supplied data, including an HTML tag name field. That field is neither validated nor escaped before being rendered on the front end, so an authenticated user with the Contributor role or higher can insert arbitrary tags, such as <script>, enabling stored XSS. The affected CPE string is cpe:2.3:a:unknown:wp_delicious:*:*:*:*:*:*:*:* (vendor not identified in NVD), and EUVD lists affected versions as WP Delicious 0 <1.10.8. The vendor advisory rates CVSS 6.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H), while our independent assessment is AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N, reflecting that a Contributor account (PR:L) is sufficient and that the stored payload can affect other users (scope change) but requires victim interaction (UI:R). CISA's SSVC decision framework records Exploitation: none, Automatable: no, and Technical Impact: total, though our independent assessment scores confidentiality and integrity impact as Low (C:L/I:L/A:N).

Know when Wp Delicious gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 6.8 MEDIUM
AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 5.4 MEDIUM

Contributor is a low-privilege authenticated role (PR:L, not PR:H); stored XSS needs victim page view (UI:R), crosses into the browser context (S:C), with limited C/I and no availability impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Sep 26, 2026 - 23:37 NVD
6.8 (None) 6.8 (MEDIUM)
Patch available
Sep 26, 2026 - 07:16 EUVD
CVE Published
Sep 26, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 26, 2026 - 06:00 cve.org
MEDIUM 6.8

DescriptionCVE.org

The WP Delicious WordPress plugin before 1.10.8 does not validate or escape the HTML tag name taken from user-supplied recipe block data before rendering it on the front end, allowing users with the Contributor role and above to inject arbitrary HTML tags, including script tags, which execute when the recipe page is viewed.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Medium
Popular WordPress recipe plugin, common on food/blog sites but niche category
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

54
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +34
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy