Drupal Advisories Flag Unsupported Projects, SQL Injection, and AI-Generated HTML

Ten Drupal.org contributed-project security advisories published on 8 July 2026 covered four Critical issues and six additional vulnerabilities across active and unsupported projects. Three Critical advisories directed site owners to uninstall unsupported projects, while the fourth addressed SQL injection in Location Selector. The remaining advisories covered cross-site scripting, cross-site request forgery, information disclosure, and access bypass.

The response paths differ across the batch. Unsupported projects have no safe advisory-listed upgrade path, so the required action is removal rather than patching. Active projects have fixed releases, but several require site teams to review exposed inputs, rendering paths, administrative permissions, or configuration-dependent attack paths.

The removal-only Critical advisories cover Commerce guest registration, Clean RESTful, and Raw Formatter [Meta Tag Formatter]. In all three cases, the Drupal Security Team says the project has a known security issue that has not been fixed by the maintainer. Commerce guest registration has a specific replacement note because the advisory points site owners to documentation for enabling account registration in checkout.

The active-project Critical advisory affects Location Selector. Drupal.org says one Views filter did not sufficiently sanitise values that may come from user input, resulting in SQL injection. The advisory says exploitation requires a View that uses the affected filter and is configured to accept user input, and the fixed release is 8.x-1.3.

AI SEO/GEO Analyzer is rated Moderately critical for cross-site scripting. The advisory says the module sends entity content and comments to a large language model, converts the model’s Markdown response to HTML, stores it, and displays the report to privileged users. That path could create stored cross-site scripting when prompt injection planted in analysed content causes unsafe markup to appear in a later report.

The AI SEO/GEO Analyzer advisory is a useful boundary case for Drupal AI security coverage. The advisory does not frame AI output itself as inherently unsafe. It points to a narrower failure: generated output was treated as display-ready HTML, while exploitation still depends on attacker-controlled text entering analysed content and prompt injection succeeding.

UI Patterns (SDC in Drupal UI) and ECA: Event - Condition - Action show how site-building layers can become security-sensitive rendering surfaces. UI Patterns is rated Moderately critical because markup passed to components was not sufficiently sanitised in some scenarios, with exploitation requiring the attacker to create or update content rendered by UI Patterns. ECA is rated Less critical for information disclosure in the Render submodule, where insufficient sanitisation of template code can matter when an ECA model uses the Render: Twig action on a data flow.

Project usage adds operational context, but it does not change advisory severity. Drupal.org project pages report 20,056 sites using ECA, 7,278 using UI Patterns, and 3,012 using AI SEO/GEO Analyzer. Those footprints make the rendering and generated-output advisories relevant to site inventories beyond the severity label alone.

The remaining active-project advisories require narrower configuration-aware review. Siteimprove Analytics is rated Moderately critical for cross-site scripting involving insufficient sanitisation of the Siteimprove Analytics identification code, with exploitation requiring the administer siteimprove_analytics permission. Ray Enterprise Translation is rated Moderately critical for cross-site request forgery on several state-changing administrative routes, and Login Disable is rated Moderately critical for an access bypass issue involving brute-force attacks against the disabled login form’s secret key.

The practical order for site owners is removal first, Critical patching next, and configuration review after that. Unsupported projects should be uninstalled rather than left in Composer because the advisory action is removal, not update. Active modules should be updated alongside checks for exposed Location Selector Views filters, AI-generated reports, UI Patterns-rendered editable content, ECA Render Twig actions, Siteimprove administrative permissions, Ray translation routes, and Login Disable secret-key protection.