dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-55880

HIGH · 7.1 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click 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. In 1.27.0 and earlier, three dashboard and note mutation functions ran their SQL without the ownership predicate that their sibling read and edit functions use: notes.delete filtered only on note id and project id, while dashboards.update_widget and dashboards.remove_widget filtered only on dashboard id and widget id, allowing any authenticated member to delete another user's private session notes and remove or rewrite widgets on another user's private dashboards.

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

OpenReplay versions 1.27.0 and earlier have a broken access control vulnerability where three mutation functions (notes.delete, dashboards.update_widget, dashboards.remove_widget) lack ownership validation predicates in their SQL queries that sibling read/edit functions properly implement. This allows any authenticated user to delete other users' private session notes and modify widgets on other users' private dashboards by exploiting the missing ownership checks.

MitigationUpgrade to a version after 1.27.0 that includes proper ownership validation predicates in the affected mutation functions, or manually add project/user ownership validation to the SQL queries for notes.delete, dashboards.update_widget, and dashboards.remove_widget.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low

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

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. Determine OpenReplay version
    Check the installed OpenReplay version by reviewing package.json, a version file, or the admin dashboard About section
    Affected if Version is 1.27.0 or earlier
  2. Verify authentication is required
    Inspect the authentication configuration or environment settings to confirm user authentication is enabled for the application
    Affected if Authentication is required (the flaw allows any authenticated user to exploit the missing checks)
  3. Inspect notes.delete for ownership validation
    Locate the notes.delete mutation function in the codebase and examine its SQL query to determine if it includes a predicate validating that the authenticated user owns the note being deleted
    Affected if The function exists and its query lacks ownership validation (no WHERE clause checking user_id matches current user)
  4. Inspect dashboards.update_widget for ownership validation
    Locate the dashboards.update_widget mutation in the codebase and examine its SQL query to determine if it validates dashboard ownership before allowing updates
    Affected if The function exists and its query does not verify the dashboard belongs to the authenticated user
  5. Inspect dashboards.remove_widget for ownership validation
    Locate the dashboards.remove_widget mutation in the codebase and examine its SQL query to determine if it validates ownership before removing widgets
    Affected if The function exists and its query lacks a check confirming the dashboard is owned by the current user

If OpenReplay version is 1.27.0 or earlier, authentication is enabled, and any of the three mutation functions lack ownership validation predicates in their SQL queries, the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a version after 1.27.0 that includes proper ownership validation predicates in the affected mutation functions, or manually add project/user ownership validation to the SQL queries for notes.delete, dashboards.update_widget, and dashboards.remove_widget.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-55880 — 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-55880 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