# CVE-2026-14933: Unblu Spark Cross-Site Scripting in Embedded Co-Browsing


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-9p8h-2662-3xvr

## What is CVE-2026-14933?

CVE-2026-14933 is a high-severity vulnerability in Unblu Spark, published on 20 Oct 2026. 

### Official description

Cross-site scripting in the embedded co-browsing feature in Unblu inc. Unblu Spark 7.0 through 7.57.7 and 8.0 through 8.39.2, on on-premises and cloud deployments, allows an unauthenticated remote attacker in the visitor role to execute arbitrary JavaScript in the browser of an agent taking part in the attacker's co-browsing session, via content of the co-browsed page that the agent's browser renders as HTML.

The JavaScript runs in the context and under the identity of the agent's session in the Agent Desk or the Single Conversation Desk.

Exploitation requires an agent to join an embedded co-browsing session with the attacker. Mobile co-apping isn't affected.

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

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


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

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

## Is CVE-2026-14933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14933 is a high-severity vulnerability in Unblu Spark, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-14933 in the wild and no public exploit code.

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

## Sources

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

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