Skip to main content

Tasty Recipes Lite CVE-2026-110026

| EUVDEUVD-2026-103391 MEDIUM
Missing Authorization (CWE-862)
2026-10-18 WPScan GHSA-38jf-fw6r-5vcj
4.9
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
    Send taxonomy term request
  3. Exploit
    Bypass missing capability check
  4. Execution
    Rename or delete arbitrary terms
  5. Impact
    Destroy categories, tags and menus

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

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 on the target WordPress site with a role as low as Contributor; the site must be running Tasty Recipes Lite prior to version 1.2.11. The plugin's taxonomy term create/rename/delete handlers omit a capability check, so any such logged-in user can manipulate terms in any taxonomy (categories, tags, navigation menus) regardless of their intended permissions. Limiting factors: exploitation is impossible without a valid low-privilege account, so sites that do not allow untrusted user registration or Contributor-level access are not practically exposed; no special non-default plugin configuration is otherwise needed.

Impact

This is a moderate, not high-priority, issue. The provided CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N, base 4.9) scores it MEDIUM, with impact limited to integrity (no confidentiality or availability loss). A key conflict exists: the vector encodes PR:H (high privileges), yet the description states exploitation is possible by a role 'as low as Contributor' - a low-privilege authenticated role. This suggests the input vector overstates the required privilege; a PR:L assessment (base ~6.5) better reflects reality, meaning the barrier to exploitation is lower than the published score implies. Publicly available exploit code exists (per WPScan), which raises practical risk, but there is NO CISA KEV listing and NO EPSS score provided, so there is no evidence of active or widespread exploitation. The vulnerability requires an attacker to already hold an authenticated account on the target site, which meaningfully limits the population of exploitable scenarios to sites that permit untrusted Contributor-level registration. Net: a real but bounded broken-access-control flaw - patch in normal cycles, prioritize on multi-author sites that accept untrusted contributors.

Exploit ScenarioDerived

An attacker registers or obtains a Contributor-level account on a WordPress site running Tasty Recipes Lite before 1.2.11 (common on multi-author food/recipe blogs). Because the plugin fails to verify user capabilities, the attacker issues requests to create, rename, or permanently delete taxonomy terms - wiping out categories, tags, or entire navigation menus to disrupt site structure. Publicly available exploit code (WPScan) lowers the skill needed to carry this out.

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

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

Alert me

AnalysisAIv1 – Oct 18, 2026

Authenticated users with as little as Contributor access can create, rename, and permanently delete taxonomy terms across any Tasty Recipes Lite site running versions before 1.2.11, because the plugin fails to enforce capability checks on those term-management actions. This permits tampering with categories, tags, and navigation menus, although exploitation requires a valid low-privilege account and the assessed risk is moderate rather than high priority. Publicly available exploit code exists, and the vendor has released 1.2.11 as the fixed version.

RemediationAI

Upgrade Tasty Recipes Lite to 1.2.11 or later; the vendor has released 1.2.11 as the fixed version, and the WPScan advisory at https://wpscan.com/vulnerability/fc8fc746-9ee1-4364-881f-28ff598f007c/ provides additional details. Until the update can be applied, reduce exposure by removing or restricting Contributor-and-above accounts on sites that do not require them, disabling open registration or moderating new users, and auditing categories, tags, and navigation menus for unauthorized changes. These controls carry trade-offs: restricting roles can disrupt legitimate editorial workflows, and disabling registration may affect community features. If term integrity is critical and upgrading is delayed, consider temporarily deactivating Tasty Recipes Lite until 1.2.11 can be installed. Because publicly available exploit code exists, prioritize the update on sites that permit low-privilege accounts.

Affected VersionsENISA

Tasty Recipes Lite 1.2 <1.2.11

Affected Packages

euvd tasty_recipes_lite fix: 1.2.11

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

Tasty Recipes Lite is a WordPress recipe plugin that manages taxonomy terms for recipe-related and standard WordPress taxonomies. The root cause is CWE-862 Missing Authorization: the handlers for creating, renaming, and deleting taxonomy terms do not perform the expected capability checks, such as current_user_can() checks for manage_categories, edit_terms, or delete_terms, before carrying out the requested action. As a result, any authenticated user who can reach the plugin's term-management functionality can manipulate terms in any taxonomy, including categories, tags, and navigation menus. The CPE entry identifies the affected package as cpe:2.3:a:unknown:tasty_recipes_lite:*:*:*:*:*:*:*:* with a wildcard version, while EUVD narrows affected releases to Tasty Recipes Lite 1.2 before 1.2.11. The independent assessment rates this as network-reachable, low complexity, and requiring only a low-privilege authenticated account, with high integrity impact and no confidentiality or availability impact.

Know when Tasty Recipes Lite 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 4.9 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N
vuln.today AI 6.5 MEDIUM

Description states a Contributor (low-privilege authenticated) suffices, so PR:L not PR:H; network-reachable with no user interaction, integrity-only impact (term tampering/deletion), no confidentiality or scope change.

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

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

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

Lifecycle Timeline

3
Patch available
Oct 18, 2026 - 07:00 EUVD
CVE Published
Oct 18, 2026 - 06:00 cve.org
MEDIUM 4.9
CVE Published
Oct 18, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

The Tasty Recipes Lite WordPress plugin before 1.2.11 does not correctly check user capabilities when creating, renaming and deleting taxonomy terms, allowing users with a role as low as Contributor to add, rename and permanently delete terms in any taxonomy on the site, including categories, tags and navigation menus.

Threat Intelligence Overview

EPSS Score
0.1%
Top 98% exploitable
Prevalence
Medium
popular WordPress recipe plugin, common on food blogs, not universal
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.1%
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
Partial

Priority Score

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

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

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