# CVE-2026-89191: Stored Cross-Site Scripting in SQLView KRIS

> An attacker with admin access can inject malicious scripts via the template name field, executing them in other users' browsers.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-j7ff-q3f2-v94q

## What is CVE-2026-89191?

CVE-2026-89191 is a medium-severity cross-site scripting vulnerability in SQLView KRIS, published on 8 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Unsanitised input in
the "template name" field of SQLView KRIS's Workflow Template feature
is rendered in "onclick" attributes on the main dashboard without
proper server-side sanitisation, allowing an attacker with administrative
access to inject and store malicious scripts that execute in the browsers of
affected users.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2026-89191 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89191 is a medium-severity cross-site scripting vulnerability in SQLView KRIS, published on 8 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-89191 in the wild and no public exploit code.

Affected product: SQLView KRIS. 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-89191/ (Markdown: https://insights.sbomify.com/CVE-2026-89191/index.md)
```

## Sources

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

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