Skip to main content

Cooked Recipe Management EUVDEUVD-2026-102610

| CVE-2026-77829 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-10-16 Wordfence GHSA-8442-fc74-434q
6.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Obtain contributor-level account
  2. Delivery
    Inject payload in [cooked-timer] shortcode content
  3. Exploit
    Submit/publish recipe page
  4. Execution
    Admin or user views injected page
  5. Persist
    Script executes in victim browser
  6. Impact
    Session hijack or privileged action

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

Exploitation requires an authenticated WordPress account with contributor-level privileges or above (per CVSS PR:L) on a site where the Cooked - Recipe Management plugin (version ≤ 1.16.1) is installed and active, and the ability to embed the [cooked-timer] shortcode within post/page/recipe content. The payload is stored and fires when any user - most impactfully an administrator - subsequently views the injected page. Limiting factors: the attacker must already possess a contributor+ account (not available to anonymous visitors unless the site permits low-trust author registration), the vulnerable plugin must be present, and successful high-impact abuse depends on a privileged user actually visiting the injected page.

Impact

This is a moderate-severity stored XSS (CVSS 6.4, CWE-79) that should be treated as a routine patch-management priority rather than an emergency. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N indicates network-reachable, low-complexity exploitation but explicitly requires PR:L - authenticated access at contributor level or above - which is the single largest limiting factor and rules out anonymous mass exploitation. The scope change (S:C) correctly reflects that injected script executes in the browser of a different user (e.g., an administrator viewing the page), but impact is capped at Low for both confidentiality and integrity with no availability impact. There is no EPSS score, no CISA KEV listing, and no public proof-of-concept in the provided data, so there is no evidence of active or widespread exploitation - the risk is latent and contingent on an attacker already holding a low-privilege account. No signals conflict here; rather, key exploitation-likelihood data (EPSS, POC) is simply ABSENT, so probability cannot be quantified. Net: a real but bounded issue, driven by the contributor-access precondition, not a high-urgency internet-wide threat.

Exploit ScenarioDerived

An attacker who holds (or registers/acquires) a WordPress account with contributor-level privileges or higher on a site running the Cooked plugin crafts a page or recipe containing a malicious [cooked-timer] shortcode whose content carries an unsanitized script payload. When an administrator or other user later views that page, the script executes in their authenticated browser session, enabling actions such as session/cookie theft or admin-context operations. No public exploit code is identified in the available data, and the required contributor account limits this to insiders or sites allowing low-trust author registration.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 16, 2026

Stored cross-site scripting in the Cooked - Recipe Management plugin for WordPress (all versions up to and including 1.16.1) lets an authenticated attacker with contributor-level access or above embed arbitrary JavaScript through the [cooked-timer] shortcode, which is stored and then executed in the browser of any user - including an administrator - who later views the injected post, page, or recipe. The root cause is insufficient input sanitization and output escaping in the plugin's shortcode handling (CWE-79), and the CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N places it at 6.4, a moderate-severity issue contingent on the attacker already holding a contributor+ account on a site running the vulnerable plugin. There is confirmed actively exploited status? No - no public exploit identified at time of analysis, and no CISA KEV listing; treat this as a routine patch-management priority rather than an emergency.

RemediationAI

No vendor-released patched plugin version is identified in the provided data; the referenced changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3729711%40cooked&new=3729711%40cooked) indicates an upstream fix in the plugin repository, so site owners should verify the current Cooked - Recipe Management plugin release on wordpress.org and the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/0592380d-fd78-48ed-a180-299fc20a41ee?source=cve) for the first version that addresses the issue, then upgrade past 1.16.1 as soon as it is confirmed. Until a confirmed patched release is applied, the most effective compensating control is to avoid assigning contributor-or-higher accounts to untrusted users, because exploitation requires that privilege level - an operational trade-off that may slow legitimate content workflows but directly removes the attack prerequisite. If the plugin is not actively needed, deactivate and remove it entirely, which eliminates the vulnerable shortcode handler; if it must stay active, audit existing posts, pages, and recipes for [cooked-timer] shortcodes containing HTML or script content and remove or HTML-escape any suspicious usage, accepting the manual review burden on large content libraries. Additional hardening includes applying a WordPress security plugin or WAF rule that filters shortcode payloads, and deploying a Content Security Policy that blocks inline script execution, though CSP requires careful tuning and can break legitimate site functionality. Note that low-trust author self-registration, if enabled, effectively grants the required contributor-level foothold and should be disabled or gated by moderation while this remains unpatched.

Affected VersionsENISA

Cooked – Recipe Management 0 ≤1.16.1

Affected Packages

euvd cooked_recipe_management no fix

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 affected software is the WordPress plugin Cooked - Recipe Management, tracked in the CPE dictionary as cpe:2.3:a:goratech:cooked_-_recipe_management, and the vulnerable component is the plugin's shortcode implementation, specifically the file includes/class.cooked-shortcodes.php at the 1.16.0 tag where the [cooked-timer] shortcode is registered and its attributes/content are rendered (referenced lines 128, 155, and 159 in the plugin's Trac browser). WordPress shortcodes are user-controllable macros expanded during the_content rendering, so content supplied inside a shortcode is a classic XSS injection surface: the plugin fails to sanitize the shortcode content on input and fails to escape it on output, allowing HTML/JavaScript to be persisted in the post content and served to every subsequent visitor. This maps to CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., cross-site scripting), and the CVSS scope-changed (S:C) rating reflects that the injected script executes in the context of the vulnerable WordPress site and can act on behalf of the victim user's session. The privilege requirement comes from the CVSS PR:L metric, meaning the attacker must be authenticated at a low-privilege level (contributor or higher, consistent with the description's 'contributor-level access and above'), and successful high-impact abuse depends on a more privileged user visiting the stored payload. No EPSS probability was supplied and no POC exploitation signal is present in the available intelligence.

Know when Wordpress Plugin 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 (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
vuln.today AI 6.4 MEDIUM

Network-reachable stored XSS requiring a contributor account (PR:L); scope changes (S:C) as script runs in another user's browser; Low C/I, no availability impact.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Cooked - Recipe Management plugin for WordPress is vulnerable to Stored Cross-Site Scripting via [cooked-timer] Shortcode Content in all versions up to, and including, 1.16.1 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Threat Intelligence Overview

EPSS Score
0.2%
Top 86% exploitable
Prevalence
Low
Niche WordPress recipe-management plugin, limited footprint versus core web stacks
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 No
EPSS 0.2%
Patch available No
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
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
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.

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

CVE-2024-5084 CRITICAL POC
9.8 May 23

The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil

CVE-2024-44000 CRITICAL POC
9.8 Oct 20

Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote

CVE-2020-36847 CRITICAL POC
9.8 Jul 12

The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner

CVE-2025-27007 CRITICAL POC
9.8 May 01

The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut

CVE-2016-1209 CRITICAL POC
9.8 May 14

The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via

CVE-2024-4443 CRITICAL POC
9.8 May 22

The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based

CVE-2024-1698 CRITICAL POC
9.8 Feb 27

SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a

CVE-2023-6875 CRITICAL POC
9.8 Jan 11

The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i

CVE-2024-1512 CRITICAL POC
9.8 Feb 17

The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base

CVE-2024-4295 CRITICAL POC
9.8 Jun 05

The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in

CVE-2024-50498 CRITICAL POC
10.0 Oct 28

Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u

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