# CVE-2026-100174: Stored Cross-Site Scripting (XSS) in AIL Framework Tag Selector via Unescaped Tag Names

> Stored XSS in AIL Framework allows attackers to execute arbitrary JavaScript in victims' browsers via malicious tag names, leading to session hijacking.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-rm3v-pc8w-cwxj

## What is CVE-2026-100174?

CVE-2026-100174 is a medium-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The AIL Framework tag selector component (var/www/static/js/tags.js) is vulnerable to stored cross-site scripting (XSS). A user with the ability to create a custom tag could embed an HTML payload containing JavaScript event handlers (e.g., <img src=x onerror=alert(1)> or <svg onload=...>) in the tag name. When another authenticated user opened a page containing the tag selector, the malicious tag name was inserted into the DOM using jQuery's html property, causing the embedded script to execute in the victim's browser context.

The vulnerable code paths affected both the suggestion/combo-item rendering (_renderComboItems) and the selected-tag rendering logic. In both cases, the display value derived from the tag's displayField was passed directly to the html property of a jQuery element constructor, which parses and inserts the string as raw HTML rather than as text.

Preconditions: the attacker must have an authenticated account with permission to create custom tags, and the victim must be an authenticated user who views a page that renders the tag selector with the attacker's stored tag. The attack is stored (persistent) and does not require the victim to perform any action beyond loading the page.

Security impact: successful exploitation allows arbitrary JavaScript execution in the victim's browser within the application's origin, potentially leading to session hijacking, unauthorized data access, form manipulation, or further client-side attacks.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-100174?


## How do I fix CVE-2026-100174?

No fix has been published for CVE-2026-100174 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100174 being exploited?

There is no known exploitation of CVE-2026-100174 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-100174 and fix it if it is affected.

What it is: CVE-2026-100174 is a medium-severity cross-site scripting vulnerability in ail framework, published on 25 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-100174 in the wild and no public exploit code.

Affected product: ail framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-100174/ (Markdown: https://insights.sbomify.com/CVE-2026-100174/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-100174
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-100174
- OSV: https://osv.dev/vulnerability/CVE-2026-100174

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-100174/
Summaries are generated and may contain mistakes; the official description above is the record.