Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as privileged Drupal user
-
DeliveryInject script into menu link attribute field
-
ExploitPayload stored in menu configuration
-
ExecutionVictim views rendered menu
-
ImpactScript executes in victim browser
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 account with the Drupal permission needed to create or edit menu links and set their attributes via the Menu Link Attributes module (reflected as PR:H in the CVSS vector). The attacker stores a script payload in a menu link attribute field; it then executes when any user who renders that menu loads the affected page. Limiting factors: the privileged permission requirement means only trusted/administrative roles can plant the payload, which substantially constrains realistic exploitation to insider-type or compromised-privileged-account scenarios; only deployments running Menu Link Attributes versions from 0.0.0 up to but not including 1.8.0 are affected. The specific attribute field and the exact permission name are not detailed in the available sources. |
| Impact | This is a genuinely low-priority issue despite being network-reachable. The signals are consistent rather than conflicting: the CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N) yields only 3.8 (Low) because exploitation requires high privileges (PR:H) and impact is partial (C:L/I:L, no availability). EPSS is 0.16% (5th percentile), KEV status is not listed, and the SSVC framework reports Exploitation: none, Automatable: no, Technical Impact: partial. The vuln.today decision label is 'monitor'. All independent signals agree this is not under active exploitation and is unlikely to be mass-exploited, consistent with a stored XSS that depends on a privileged account to plant the payload. The main caveat is that the raw description does not specify which Drupal permission is required to set menu link attributes, so the PR:H assumption cannot be independently confirmed from the text alone; the referenced Drupal advisory (SA-contrib-2026-209) should be consulted to confirm the exact permission. No special caveats about data conflicts otherwise - this is a real but low-severity hardening fix, not an emergency. |
| Exploit ScenarioDerived | An authenticated Drupal user who holds the privileged permission to configure menu links edits a menu link's attributes and stores a malicious script payload in one of the attribute fields. When another user - potentially an administrator - later views a page that renders that menu, the script executes in their browser session, enabling actions such as session/cookie theft or performing requests as the victim. No public exploit code was identified in the provided sources. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 30, 2026
Stored cross-site scripting in the Drupal contributed module Menu Link Attributes (versions 0.0.0 through 1.8.0) lets an attacker persist a script payload inside a menu link attribute, which then executes in the browser of any user who renders that menu. Exploitation requires an authenticated account holding the Drupal permission to create or edit menu links and set their attributes (PR:H in the CVSS vector), so realistic abuse is limited to insider or compromised-privileged-account scenarios rather than anonymous visitors. Severity is low (CVSS 3.8, EPSS 0.16%, 5th percentile), CISA SSVC records no known exploitation and no automatable path, the project's priority label is monitor, and a vendor patch is available; no public exploit has been identified at time of analysis.
RemediationAI
Patch available per vendor advisory: update the Menu Link Attributes module to a release at or above 1.8.0, the first version outside the affected range listed by EUVD, following the instructions in Drupal's security advisory https://www.drupal.org/sa-contrib-2026-209 (mirrored by NVD at https://nvd.nist.gov/vuln/detail/CVE-2026-107306). Because the payload is stored in menu link configuration, review existing menu links for unexpected attribute values after upgrading. As a compensating control while patching, restrict the Drupal permission that allows creating or editing menu links and setting their attributes to a small set of trusted roles, understanding the trade-off that legitimate editors lose the ability to manage menu attributes; this reduces the pool of accounts that can plant a payload but does not remove the escaping defect itself. Priority is monitor: exploitation requires a privileged account, no public exploit has been identified at time of analysis, and EPSS is 0.16%.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Menu Link Attributes is a Drupal contributed module (CPE cpe:2.3:a:drupal:menu_link_attributes) that extends Drupal's menu link entities so editors can attach HTML attributes - such as classes, target, rel or ARIA values - to individual menu links. The flaw is CWE-79, improper neutralization of input during web page generation: attribute values supplied through the module are not adequately escaped when the menu is rendered into HTML, so markup injected into an attribute field is emitted into the page and interpreted by the browser. Because the payload is persisted in the menu link configuration rather than reflected per request, every page render that outputs the affected menu serves the script to viewers, satisfying the stored-XSS pattern. The trigger details - the exact attribute field and permission machine name - are not described in the available sources. Our independent assessment scores the vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N, differing from the NVD-style 3.8 vector (S:U) by treating the injected script as crossing a scope boundary from the module's attribute handling into the broader site origin; both agree on network reachability, low attack complexity, high privileges required, and low confidentiality and integrity impact with no availability impact.
Know when Menu Link Attributes 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:H/UI:N/S:U/C:L/I:L/A:N
Privileged account needed to store the payload (PR:H); stored XSS runs in another user's browser context, so scope changes (S:C) with low confidentiality/integrity impact and no availability impact.
Primary rating from Vendor (drupal).
CVSS VectorVendor: drupal
Lifecycle Timeline
3DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Menu Link Attributes allows Stored XSS. This issue affects Menu Link Attributes versions: from 0.0.0 to 1.8.0.
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.
EUVD-2026-113566
GHSA-34jp-3hpv-473h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB