dbcve.org
Ui IconsDrupal extension · Beyris

CVE-2026-2349

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 1.0.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Icons allows Cross-Site Scripting (XSS).This issue affects UI Icons: from 0.0.0 before 1.0.1, from 1.1.0 before 1.1.1.

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 · high confidence

A reflected Cross-site Scripting (XSS) vulnerability exists in the Drupal UI Icons module due to improper input neutralization during web page generation. The vulnerability allows unauthenticated attackers to inject malicious JavaScript code through icon parameters that are rendered without proper encoding. Affected versions are 0.x before 1.0.1 and 1.x before 1.1.1.

MitigationUpgrade the Drupal UI Icons module to version 1.0.1 or later for the 0.x branch, or 1.1.1 or later for the 1.x branch. Ensure all user-supplied input is properly sanitized before rendering in the icon subsystem.

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 IconsDrupal extension
Affected:< 1.0.1= 1.1.0

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Verify if Beyris Ui Icons module is installed
    Check the Drupal modules directory for the ui_icons module or run 'drush pm:list --status=enabled' to list enabled modules. Also check composer.json for 'beyris/ui_icons' dependency.
    Affected if The module is present and enabled in Drupal
  2. Determine the installed version of Beyris Ui Icons
    Read the version from the module's .info.yml file in the ui_icons directory, from composer.lock, or run 'drush pm:list' which shows version numbers. The version is typically listed in the module's info file or in the Drupal admin interface at /admin/modules.
    Affected if Version is 0.x before 1.0.1, or 1.x at 1.1.0 (exactly)
  3. Identify if icon rendering is exposed to user input
    Examine the module's routing file (ui_icons.routing.yml) and controller code to determine which routes handle icon parameter rendering. Check if any routes accept URL parameters that are used in icon rendering without sanitization.
    Affected if The module exposes routes that accept user-supplied parameters for icon display without proper encoding
  4. Check for custom icon implementations using the module
    Review custom modules or themes that integrate with the UI Icons functionality to see if they pass unsanitized user input to icon rendering functions. Search code for calls to icon render methods with $_GET, $_POST, or request parameters.
    Affected if Custom code passes raw user input to icon rendering without sanitization
  5. Verify input handling in icon parameter processing
    Review the module's source code, specifically any functions that process icon parameters (like name, id, or style parameters) and check if they use proper output encoding (like \Drupal\Component\Utility\Html::escape() or render arrays with #plain_text) before outputting.
    Affected if Icon parameter processing lacks proper output encoding and is accessible to unauthenticated users

You are affected if Beyris Ui Icons module version is below 1.0.1 for 0.x branches or is exactly 1.1.0 for 1.x branches, and the icon parameter rendering is accessible to unauthenticated users without proper sanitization.

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 1.0.1 or later
Fixed in 1.0.1
Interim mitigation

Upgrade the Drupal UI Icons module to version 1.0.1 or later for the 0.x branch, or 1.1.1 or later for the 1.x branch. Ensure all user-supplied input is properly sanitized before rendering in the icon subsystem.

Recommended fix High confidence

1.1.1 or later

  1. Back up your Drupal site database and files
  2. Use Composer to update the UI Icons module: composer require drupal/ui_icons:^1.1.1
  3. Run database updates using drush updatedb or via the web interface at /update.php
  4. Clear Drupal cache using drush cr or via the admin interface

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

Fix this in Ui Icons Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2349 — 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-2349 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