Stored XSS via insufficient component markup sanitization
Published Jul 10, 2026 · Updated Jul 10, 2026
Stored XSS in Drupal UI Patterns 2.0.0 through 2.0.16 allows remote authenticated users to execute script via component markup. The component rendering path passes attacker-controlled markup without sufficient sanitization, so it is stored and later interpreted in a viewer's browser. Exploitation requires permission to create or update content rendered by UI Patterns and affects users who view that content.
Summary
What happened
Stored XSS in Drupal UI Patterns 2.0.0 through 2.0.16 allows remote authenticated users to execute script via component markup. The component rendering path passes attacker-controlled markup without sufficient sanitization, so it is stored and later interpreted in a viewer's browser. Exploitation requires permission to create or update content rendered by UI Patterns and affects users who view that content.
The record
- CVE
- CVE-2026-15084
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- Avatar Uploader Project
- Product
- UI Patterns (SDC in Drupal UI)
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0 <2.0.17
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo