# CVE-2026-55879: OpenReplay: Unauthenticated stored XSS leads to dashboard account takeover

> Unauthenticated attackers can inject scripts via custom events to steal session tokens and take over OpenReplay dashboard accounts.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 13 Jul 2026
- **Also known as:** GHSA-3mfc-7hf4-jfxh

## What is CVE-2026-55879?

CVE-2026-55879 is a critical cross-site scripting vulnerability in openreplay, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

OpenReplay is a self-hosted session replay suite. From 1.24.0 before 1.25.0, the OpenReplay tracking SDK accepts custom event names and captured page URLs from any visitor using a public project key, stores them in ClickHouse without output encoding, and later renders them in the authenticated dashboard through TextEllipsis and the event-details modal, allowing an unauthenticated attacker to store script that executes in the dashboard origin, reads the session JWT from localStorage, and takes over a dashboard account. This issue is fixed in version 1.25.0.

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

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


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

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

## Is CVE-2026-55879 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55879 is a critical cross-site scripting vulnerability in openreplay, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-55879 in the wild and no public exploit code.

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

## Sources

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

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