dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-45297

MEDIUM · 5.3 CVSS v4.0 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

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. Prior to 1.26.0, there is a cross-tenant IDOR on feature-flag and assist-stats routes via {project_id} case mismatch. ProjectAuthorizer.__call__ (OSS api/auth/auth_project.py:14-38 and EE ee/api/auth/auth_project.py:14-46) only runs projects.is_authorized(project_id, tenant_id, user_id) + projects.get_project(tenant_id, project_id) when self.project_identifier == "projectId" (camelCase). For EE multi-tenant, feature-flag queries only filter on project_id, never tenant_id. Any authenticated user in tenant A can read/update/delete feature-flag rows belonging to tenant B by iterating the sequential integer project_id + feature_flag_id. OSS is single-tenant by design ({"errors":["tenants already registered"]} on second signup) so there's no cross-tenant impact This vulnerability is fixed in 1.26.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

OpenReplay before 1.26.0 contains an IDOR vulnerability where the ProjectAuthorizer authorization check only executes when the project identifier uses camelCase ('projectId'), but the API accepts both camelCase and other case variations. For multi-tenant EE deployments, feature-flag and assist-stats routes fail to filter queries by tenant_id, allowing any authenticated user to access/modify resources in other tenants by iterating project_id and feature_flag_id values.

MitigationUpgrade to OpenReplay version 1.26.0 or later. For EE multi-tenant deployments, verify that authorization checks consistently run regardless of parameter casing and that queries properly filter by tenant_id.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 version
    Check the installed OpenReplay version by accessing the /api/version endpoint, checking the frontend UI footer, or inspecting the Docker/ deployment manifests
    Affected if Version is before 1.26.0 (e.g., 1.25.0, 1.24.0, etc.)
  2. Confirm multi-tenant EE deployment
    Verify if this is an Enterprise Edition (EE) installation with multi-tenancy enabled, typically indicated by tenant configuration or multiple organization setups
    Affected if Running EE version with multi-tenant configuration enabled
  3. Inspect API route handlers
    Examine the feature-flag and assist-stats route handlers in the codebase or API configuration to determine if tenant_id filtering is implemented
    Affected if Routes exist but lack tenant_id filtering in database queries
  4. Test parameter case handling
    Send API requests using non-camelCase project identifiers (e.g., projectid, project_id, PROJECTID) to the affected routes and observe if authorization is properly enforced
    Affected if Requests with non-camelCase project identifiers bypass the ProjectAuthorizer check and return data from other tenants
  5. Verify authenticated user access scope
    As a low-privileged authenticated user, attempt to iterate project_id and feature_flag_id values to access resources belonging to different tenants
    Affected if User can access or modify resources belonging to other tenants by manipulating these ID values

The environment is affected if running OpenReplay EE before version 1.26.0 with multi-tenancy enabled, where non-camelCase project identifiers bypass authorization checks on feature-flag and assist-stats routes.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to OpenReplay version 1.26.0 or later. For EE multi-tenant deployments, verify that authorization checks consistently run regardless of parameter casing and that queries properly filter by tenant_id.

Recommended fix High confidence

1.26.0

  1. 1. Identify your current OpenReplay installation version.
  2. 2. For Enterprise Edition (EE) deployments, upgrade to version 1.26.0 or later.
  3. 3. Verify the upgrade was successful by checking the OpenReplay version.
  4. 4. Test that the authorization is now properly enforced on feature-flag and assist-stats routes.
Caveat Review release notes for any breaking changes between your current version and 1.26.0 before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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