dbcve.org
Ui PatternsDrupal extension · Ademarco

CVE-2026-15084

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 2.0.17 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Neutralization of Input During Web Page Generation ("Cross-site Scripting") vulnerability in Drupal UI Patterns (SDC in Drupal UI) allows Stored XSS. This issue affects UI Patterns (SDC in Drupal UI) versions: from 2.0.0 to 2.0.17.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stored XSS vulnerability in Drupal UI Patterns module (SDC component) versions 2.0.0 through 2.0.17 allows authenticated attackers to inject malicious JavaScript code that persists on the server and executes in victims' browsers when viewing affected pages.

MitigationUpdate UI Patterns module to version 2.0.18 or later which contains the fix for this stored XSS vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ui PatternsDrupal extension
Affected:>= 2.0.0, < 2.0.17

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate UI Patterns module directory
    Search for the 'ui_patterns' directory in your Drupal installation, typically under sites/all/modules/contrib/, web/modules/contrib/, or modules/contrib/. Check the .info.yml file inside for module metadata.
    Affected if The ui_patterns directory exists and contains module files
  2. Determine installed UI Patterns version
    Open the ui_patterns.info.yml or ui_patterns.module file and look for the version declaration. Alternatively, check CHANGELOG.txt or the module's composer.json for the exact version number.
    Affected if Version is 2.0.0 through 2.0.17 (inclusive)
  3. Verify UI Patterns module is enabled
    Run 'drush pm-list --status=enabled' or check the Drupal admin UI at /admin/modules to confirm ui_patterns is listed as enabled.
    Affected if Module is listed as enabled in the Drupal system
  4. Check for SDC component usage
    Look for SDC (SDC component) related configuration or templates in your Drupal site. Search for references to 'sdc' in configuration files (config/sync/) or within the ui_patterns module's templates/ directory.
    Affected if SDC component templates or configurations are present in the installation
  5. Inspect for suspicious stored patterns
    Review any custom UI Patterns configurations stored in the database or configuration files. Query the 'config' table for entries containing 'ui_patterns' and inspect stored pattern definitions for unexpected script tags or event handlers.
    Affected if Pattern definitions contain raw HTML, script tags, or JavaScript event handlers in fields that accept user input

The environment is affected if UI Patterns module version 2.0.0-2.0.17 is installed, enabled, and SDC component is in use, with any user-supplied pattern data potentially containing malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.17 or later
Fixed in 2.0.17
Interim mitigation

Update UI Patterns module to version 2.0.18 or later which contains the fix for this stored XSS vulnerability.

Recommended fix Moderate confidence

2.0.18 or later

  1. 1. Back up your Drupal site database and files before making any changes.
  2. 2. Navigate to your Drupal project's composer.json directory.
  3. 3. Run 'composer require drupal/ui_patterns:^2.0.18' to update to the fixed version, or use 'composer update drupal/ui_patterns --with-all-dependencies' to update to the latest available version.
  4. 4. Clear Drupal caches using 'drush cr' or through the Drupal admin interface at /admin/config/development/performance.
  5. 5. Verify the update was successful by checking the UI Patterns version at /admin/reports/status or via composer.
  6. 6. Test the UI Patterns functionality in your site to ensure the update did not break existing components.
Caveat Review release notes for any breaking changes between your current version and 2.0.18+; minor version updates typically maintain backward compatibility but custom pattern implementations may need testing.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ui Patterns Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15084 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data