CVE-2026-28443
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 · uneditedOpenReplay is a self-hosted session replay suite. Prior to version 1.20.0, the POST /{projectId}/cards/search endpoint has a SQL injection in the sort.field parameter. This issue has been patched in version 1.20.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 confidenceA SQL injection vulnerability exists in the sort.field parameter of the POST /{projectId}/cards/search endpoint in OpenReplay versions prior to 1.20.0. An attacker can inject malicious SQL queries through this parameter to manipulate database operations, potentially exfiltrating sensitive data or compromising the underlying database. The critical CVSS score of 9.8 indicates the vulnerability is easily exploitable and has severe impact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.20.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check OpenReplay versionIdentify the installed OpenReplay version by inspecting the package.json file, Docker container labels, the administration UI version display, or querying the API health endpoint for version information.Affected if The installed version is below 1.20.0 (e.g., 1.19.x, 1.18.x, etc.)
-
Verify cards/search endpoint availabilityConfirm that the POST /{projectId}/cards/search endpoint is accessible in your OpenReplay instance by reviewing your web server routing configuration or API gateway rules.Affected if The endpoint is exposed and responds to POST requests (even if authentication is required, the vulnerability exists in the code)
-
Identify if projectId parameter usage is activeCheck if projects are created in the OpenReplay instance, as the vulnerable endpoint requires a valid projectId to be used.Affected if Any projects exist in the system, meaning the cards/search endpoint can be invoked with a project identifier
You are affected if your OpenReplay installation version is below 1.20.0 and you have any projects configured in the system, as the SQL injection vulnerability in the sort.field parameter of the cards/search endpoint is present in those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.20.0
Upgrade OpenReplay to version 1.20.0 or later to apply the security patch that addresses the SQL injection vulnerability in the sort.field parameter.
OpenReplay 1.20.0
- Upgrade OpenReplay to version 1.20.0 or later to patch the SQL injection vulnerability in the POST /{projectId}/cards/search endpoint's sort.field parameter
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28443 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28443 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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