Drupal AI EUVD-2026-43058

Exploitation requires that the target Drupal site has the AI (Artificial Intelligence) contributed module installed and enabled in an affected version (0.0.0-pre-1.2.17, 1.3.0-pre-1.3.8, or 1.4.0-pre-1.4.3). The victim must interact with a page or URL that causes the module to render unsanitized input in the browser - this constitutes the required user interaction (UI:R). The attacker requires no authentication (PR:N) and no special account on the target site. Exploitation is limited by: the module must be installed (not present in default Drupal installations), a victim must be induced to visit the malicious URL or interact with the affected page, and impact is bounded to the browser session context rather than direct server-side code execution.

Real-world risk is moderate despite a medium CVSS of 6.1. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C) confirms network-accessible, low-complexity exploitation requiring no authentication, but the mandatory user interaction (UI:R) is the key limiting factor - a victim must navigate to or interact with a crafted or compromised page. EPSS at 0.16% (6th percentile) aligns with no observed exploitation in the wild and no KEV listing, indicating this has not been operationalized by threat actors as of this analysis. No public POC is referenced in the available intelligence. The combination of PR:N and AV:N means the attack surface is broad for any internet-facing Drupal site running the AI module, but the UI:R requirement reduces the likelihood of opportunistic mass exploitation compared to a fully unauthenticated, no-interaction flaw. The confidentiality and integrity impacts are limited (C:L/I:L), consistent with session theft or targeted page defacement rather than full server compromise. Overall, this is a credible phishing-amplification or session-hijacking risk for sites exposing AI module functionality to untrusted users, but not an imminent mass-exploitation priority given current signals.

An attacker crafts a malicious URL or submits input to a Drupal page that triggers the AI module to reflect unsanitized content back into the HTML response. When a logged-in Drupal user (such as a site administrator or editor) is socially engineered into visiting the crafted URL, the injected JavaScript executes in their browser, potentially stealing their session cookie or performing privileged actions on their behalf within the Drupal site. No public proof-of-concept code is referenced in the available intelligence, but the attack complexity is low once the injectable parameter is identified.