Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XSS payload
-
DeliveryDeliver via link or injected input
-
ExploitVictim loads affected plugin page
-
ExecutionScript executes in victim browser context
-
ImpactHijack session or perform actions
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 the Food Menu - Restaurant Menu & Online Ordering for WooCommerce plugin (version 6.0.5 or earlier) installed on a WordPress/WooCommerce site, and - per the CVSS UI:R metric - requires a victim to interact with attacker-controlled content (e.g., clicking a crafted link or viewing a page containing the injected payload). No authentication is required of the attacker (PR:N), so the entry point is reachable by anonymous users, but the limiting factor is that impact only materializes when a user (ideally a privileged one) loads the malicious content; no payoff occurs without that interaction. The description does not name a specific feature or non-default setting as a precondition, so exploitation appears tied to the plugin's standard menu/ordering input handling rather than an optional configuration mode. |
| Impact | This is a genuinely medium-tier issue rather than a top-priority emergency, and the signals are internally consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, 7.1) describes an unauthenticated, network-reachable XSS that is low-complexity but requires victim user interaction and yields only Low impact to each of confidentiality, integrity, and availability - the elevated score is driven primarily by the scope change (S:C), typical of XSS where injected script executes in a separate security context (the victim's browser). No EPSS probability was supplied in the input, the CVE is not listed in CISA KEV, and no public proof-of-concept is referenced (only the Patchstack database advisory), so the correct exploitation status is 'no public exploit identified at time of analysis.' There is no conflict between the signals, but the ABSENCE of EPSS/KEV/POC data means real-world exploitation likelihood cannot be quantified from the input and must be treated as unknown rather than low. Net: a real but moderate web-application flaw whose impact is bounded by the need for user interaction and the Low (not High) CIA ratings. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a URL or input that reflects/stores malicious JavaScript through the Food Menu plugin, then lures a logged-in site visitor or administrator into loading the affected page. When the victim's browser renders the page, the script executes in their session context, enabling actions such as cookie/session theft or forced administrative actions. No public exploit code is identified at time of analysis, and successful exploitation depends on the victim interacting with the attacker-supplied content. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated cross-site scripting in the Food Menu - Restaurant Menu & Online Ordering for WooCommerce plugin (versions up to and including 6.0.5) lets attackers inject script that executes in the context of a victim's browser session on an affected WordPress/WooCommerce site. Affected deployments are any WordPress installation running the RadiusTheme plugin at version 6.0.5 or earlier; the attacker needs no credentials (CVSS PR:N) but the payload only fires when a victim loads attacker-influenced content (UI:R), so a privileged user such as an administrator is the highest-value target. There is no CISA KEV entry and no public exploit code identified in the supplied intelligence at time of analysis, and no EPSS score was provided; our independent assessment rates this as a genuine medium-tier issue rather than an emergency, with the vector (scope change S:C, low confidentiality/integrity/availability impact) internally consistent with a script-injection flaw. Patchstack is credited as the reporting source and hosts the reference advisory. Vendor-released patch: no fixed version identified in the available data.
RemediationAI
No vendor-released patched version is identified in the provided intelligence data, so the first action is to confirm the vulnerability status and any fixed release directly with RadiusTheme and on the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/tlp-food-menu/vulnerability/wordpress-food-menu-restaurant-menu-online-ordering-for-woocommerce-plugin-6-0-5-cross-site-scripting-xss-vulnerability, then upgrade the plugin to the first release that Patchstack or the vendor lists as fixed; do not treat version 6.0.5 or earlier as safe. If no patched release exists yet, consider temporarily deactivating the plugin on sites where the menu/ordering functionality is not business-critical, accepting the loss of those front-end features as the trade-off, or, where it must stay live, apply virtual patching through a WAF or a WordPress-specific managed rule set such as Patchstack's own protection to block XSS payloads targeting the plugin's input paths, understanding that signature-based blocking may miss novel encodings. Restrict the exposure created by the required user interaction: limit who browses untrusted links while authenticated, avoid clicking external links from within an active wp-admin session, and consider enforcing a Content Security Policy that disallows inline and third-party script, with the caveat that aggressive CSP settings frequently break legitimate inline scripts from other plugins and themes and must be tested in report-only mode first. Additional hardening that reduces the payoff of a successful injection includes enabling HttpOnly and SameSite attributes on WordPress authentication cookies, rotating administrator sessions and salts if compromise is suspected, keeping WordPress, WooCommerce and all other plugins current, and reviewing wp-admin user accounts for unexpected additions. Because exploitation requires user interaction and no public exploit or KEV listing was identified at time of analysis, remediation can proceed on a normal patch cadence rather than an emergency one, but the plugin should still be inventoried across all managed sites to determine how many are running 6.0.5 or earlier.
Affected VersionsENISA
Affected Packages
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, in a WordPress plugin that renders restaurant menus and WooCommerce online-ordering interfaces. The plugin accepts input through its menu/ordering handling paths and reflects or embeds it into generated HTML without adequate escaping or sanitization, so attacker-supplied markup is parsed as executable script in the victim's browser rather than as inert text. The CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L vector describes a network-reachable, low-complexity attack that requires no authentication on the attacker's side but depends on a user interacting with the crafted content; the Changed scope metric (S:C) means the script escapes the security context of the vulnerable plugin component and runs with the privileges of the hosting site's origin, which is why an injected payload can act on behalf of an authenticated WordPress or WooCommerce administrator. Impact is limited to Low on confidentiality, integrity and availability individually, consistent with typical XSS consequences such as session/cookie theft, CSRF-style administrative actions, credential harvesting via injected forms, or content defacement rather than full server compromise. The CPE string cpe:2.3:a:radiustheme:food_menu_-_restaurant_menu_&_online_ordering_for_woocommerce confirms RadiusTheme as the vendor, and the Patchstack reference is filed under the plugin slug tlp-food-menu. Because the disclosure names no specific shortcode, REST route or non-default setting as a precondition, the flaw appears tied to the plugin's standard menu/ordering input handling rather than an opt-in configuration mode. No CVSS vector element indicates a local or adjacent attack path; exploitation is remote and delivered through the web front end.
Know when Woocommerce 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
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Unauthenticated network-reachable XSS (AV:N/PR:N) needs victim interaction (UI:R); script runs in the browser's separate context (S:C) with limited Low CIA impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Food Menu - Restaurant Menu & Online Ordering for WooCommerce <= 6.0.5 versions.
Executive ViewAI
The Food Menu - Restaurant Menu & Online Ordering for WooCommerce plugin (versions up to and including 6.0.5) exposes WordPress/WooCommerce sites to unauthenticated script injection that can execute in a victim's browser session, with administrators the highest-value target. No public exploit identified at time of analysis, but no vendor-released patch identified at time of analysis, and because the flaw affects e-commerce storefronts, leadership should treat this as a medium-tier operational risk requiring immediate inventory and mitigation rather than an emergency. Organizations running this plugin should prioritize identifying exposed sites, reducing admin exposure, and applying interim controls until a fix is released.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing the plugin if not required, applying WAF/virtual patching rules to block script injection against the affected plugin, enforcing least privilege and MFA for WordPress administrators, restricting admin access by IP, and monitoring logs for XSS exploitation attempts.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Woocommerce
View allThe WooCommerce plugin through 3.x for WordPress has a Directory Traversal Vulnerability via a /wp-content/plugins/wooco
Unauthenticated arbitrary file upload in Addify's Request a Quote for WooCommerce plugin, affecting all versions up to a
The WooCommerce Help Scout WordPress plugin before 2.9.1 (https://woocommerce.com/products/woocommerce-help-scout/) allo
WooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary PHP code by
Unauthenticated path traversal in OrderConvo (the "Admin and Customer Messages After Order for WooCommerce" plugin), aff
Unauthenticated remote attackers can seize control of the payment configuration on WordPress stores running the Fundiin
Ultimate WooCommerce Gift Cards 3.0.2 is affected by a file upload vulnerability in the Custom GiftCard Template that ca
Unauthenticated attackers can exploit the Walletdoc Payment Gateway for WooCommerce plugin before version 1.8.5 to execu
Unauthenticated SQL injection in the ELEX WooCommerce Request a Quote WordPress plugin (all versions before 2.4.1) allow
Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync
Unauth. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low atta
An issue was discovered in the NAB Transact extension 2.1.0 for the WooCommerce plugin for WordPress. Rated high severit
EUVD-2026-96444
GHSA-c4q9-q8mr-88fg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB