dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-55879

CRITICAL · 9.3 CVSS v3.1 Published 2026-07-10
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Patch available 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored XSS vulnerability in OpenReplay's tracking SDK (versions 1.24.0 before 1.25.0) allows unauthenticated attackers to inject malicious JavaScript via custom event names or page URLs using a public project key. The unsanitized input is stored in ClickHouse and executed when viewed in the authenticated dashboard, enabling attackers to steal session JWTs from localStorage and hijack dashboard accounts.

MitigationUpgrade to OpenReplay version 1.25.0 or later to implement proper input sanitization and output encoding. As a temporary mitigation, consider restricting or rotating public project keys to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OpenReplay installation and version
    Check your OpenReplay deployment for the installed version. If using Docker, run 'docker ps' and inspect the container image tags, or check package.json/package-lock.json if self-building the tracking SDK. If using the hosted service, contact your OpenReplay administrator to confirm the version.
    Affected if The installed version is 1.24.0 or any version before 1.25.0.
  2. Confirm tracking SDK is in use
    Inspect your web application source code for the OpenReplay tracking snippet. Look for a script tag loading from your OpenReplay instance that initializes the tracker, typically containing 'init({ projectKey: ... })'.
    Affected if The OpenReplay JavaScript tracker is deployed on any frontend application.
  3. Verify public project key configuration
    Locate the projectKey value passed to the OpenReplay init() function in your tracking snippet. This is the public key that can be used to send data without authentication.
    Affected if A valid public project key is configured and accessible in client-side code.
  4. Confirm ClickHouse storage backend
    Check your OpenReplay backend configuration for the storage settings. In the docker-compose.yml or environment variables, look for ClickHouse connection details (typically port 8123) or the OR_STORAGE_CLICKHOUSE environment variable.
    Affected if ClickHouse is configured as the session storage backend (the default configuration).

Your environment is affected if OpenReplay version 1.24.0 or earlier is deployed with the JavaScript tracking SDK and ClickHouse storage, since an attacker with a public project key can inject malicious scripts that execute in the dashboard.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to OpenReplay version 1.25.0 or later to implement proper input sanitization and output encoding. As a temporary mitigation, consider restricting or rotating public project keys to limit attack surface.

Recommended fix High confidence

1.25.0

  1. Upgrade OpenReplay to version 1.25.0 or later
  2. Consult the official OpenReplay upgrade documentation for your deployment method (Docker, Kubernetes, etc.)
  3. After upgrading, verify the dashboard loads correctly and session replay functionality works as expected
  4. Ensure all dashboard users re-authenticate after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,500
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-55879 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data