# CVE-2026-36214: Cross-site scripting in osTicket

> Remote attackers can execute arbitrary JavaScript in Agent or Admin sessions via stored XSS in osTicket, potentially leading to account takeover.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 4 Aug 2026
- **Also known as:** GHSA-ffr2-xp93-qf4x

## What is CVE-2026-36214?

CVE-2026-36214 is a medium-severity cross-site scripting vulnerability in osTicket, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

osTicket versions from 1.10 up to 1.17.7 and from 1.18.0 up to 1.18.3 are vulnerable to a stored XSS due to a vulnerable Bootstrap Tooltip component and insufficient HTML sanitization, allowing remote attackers to execute arbitrary JavaScript in Agent or Admin sessions.

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

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


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

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

## Is CVE-2026-36214 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36214 exists.

Public exploit code:

- Stored Cross-Site Scripting (XSS) in osTicket via Vulnerable Bootstrap Tooltip Component (github_poc): https://github.com/WesWrench/CVE-2026-36214

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36214 is a medium-severity cross-site scripting vulnerability in osTicket, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-36214 exists.

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

## Sources

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

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