Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify Drupal site running Orejime module
-
DeliveryCraft URL with XSS payload in vulnerable Orejime parameter
-
ExploitDeliver malicious link to target user
-
ExecutionVictim loads page, payload renders in browser
-
PersistScript executes in victim's session context
-
ImpactExfiltrate cookies or perform authenticated 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 | User interaction is required - the victim must follow a crafted link or visit a page where the malicious payload is rendered (UI:R per CVSS vector). No authentication is required from the attacker's side (PR:N). The Orejime module must be installed and active on the target Drupal site, which is a non-default configuration since Orejime is a contributed (not core) module. Exploitation is limited to Drupal sites running Orejime versions 0.0.0 through 2.0.15. The changed scope (S:C) means impact extends beyond just the page with the injection point, but the CVSS C:L/I:L bounds the per-exploitation impact to partial confidentiality and integrity loss rather than full compromise. |
| Impact | The CVSS base score of 6.1 (Medium) is directionally appropriate but requires contextual interpretation. The vector confirms network-exploitable, low-complexity, no-privilege-required access with user interaction needed - meaning an attacker must induce a victim to load a crafted URL or interact with a malicious page. The changed scope elevates the impact beyond a simple reflected XSS. Against these signals, the EPSS of 0.03% (8th percentile) indicates very low observed exploitation probability in the wild, KEV status is not listed (no confirmed active exploitation), and no public POC is known. The realistic priority is moderate for Drupal sites handling authenticated user sessions or sensitive data via cookie-consent flows: XSS with S:C can enable session theft, credential harvesting via injected forms, or defacement. For sites where the Orejime banner is visible to unauthenticated visitors, the attack surface is broad but the impact per the CVSS (C:L/I:L) is constrained. No conflicting signals between CVSS vector and description are apparent. |
| Exploit ScenarioDerived | An attacker crafts a URL or link containing a malicious JavaScript payload targeting an Orejime input parameter - such as a cookie name, preference value, or banner configuration reflected in the page. When a site visitor clicks the link or visits the crafted page, the injected script executes in their browser within the scope of the target Drupal site, potentially exfiltrating session cookies or performing actions on behalf of the victim. No public POC is known, but the attack complexity is low per CVSS (AC:L), meaning exploitation requires no special conditions beyond delivering the link to a victim. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 20, 2026
Reflected or stored cross-site scripting in Drupal's Orejime cookie consent module (versions 0.0.0 through 2.0.15) allows unauthenticated remote attackers to inject malicious scripts that execute in a victim's browser upon page load or link interaction. The changed scope (S:C) in the CVSS vector indicates the injected script executes in a security context beyond the originating page - consistent with a consent banner or cookie-preference widget that renders across site sections. No public exploit code has been identified at time of analysis, and EPSS is 0.03% (8th percentile), placing this in the low-exploitation-probability tier despite being network-accessible with no authentication required.
RemediationAI
Upgrade Drupal Orejime to version 2.0.16 or later, which is the vendor-released patch per Drupal security advisory SA-contrib-2026-032 (https://www.drupal.org/sa-contrib-2026-032). The fix version 2.0.16 is confirmed as the boundary in the affected versions data (0.0.0 before 2.0.16). If an immediate upgrade is not feasible, a compensating control is to temporarily disable the Orejime module in Drupal's module administration until patching is possible - note this will remove the cookie consent banner, which may have GDPR compliance implications. Restricting access to any Orejime configuration pages to authenticated administrators reduces the input surface but does not eliminate risk if the injection point is in user-facing banner parameters. There is no evidence that WAF rules for generic XSS payloads would reliably block exploitation without the vendor patch given the module-specific injection context.
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
Orejime is a Drupal contributed module implementing GDPR/cookie-consent banner functionality (CWE-79: Improper Neutralization of Input During Web Page Generation). The CPE string cpe:2.3:a:drupal:orejime:*:*:*:*:*:*:*:* covers all versions prior to 2.0.16. The root cause is insufficient sanitization or escaping of user-controlled input before it is reflected or stored and rendered in the browser's DOM - a classic CWE-79 pattern. The changed scope (S:C) in the CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N vector signals the payload executes in a context that differs from where the injection point resides, which for a site-wide cookie consent component could mean the injected script affects rendering across multiple pages or origins. This is consistent with a widget that persists user preferences in storage and re-renders them on subsequent page loads.
Know when Orejime 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:N
Primary rating from Vendor (drupal) · only source for this CVE.
CVSS VectorVendor: drupal
Lifecycle Timeline
3DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal Orejime allows Cross-Site Scripting (XSS).
This issue affects Orejime: from 0.0.0 before 2.0.16.
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-30997
GHSA-6g8q-jh52-g228
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB