CVE
OpenEMR patient data exposure via SQL injection in OnsiteDocument
Only affects OpenEMR before 8.5.0 with the Patient Portal enabled (portal_onsite_two_enable=1). Fixed in 8.5.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.5.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Patient Portal enabled (portal_onsite_two_enable=1) OpenEMR 8.1.0 and earlier, per the advisory body
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.38% · 32nd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Authenticated patients of the OpenEMR patient portal (before version 8.5.0) can remotely send crafted requests to the OnsiteDocument.Query endpoint, which is not properly protected against SQL injection. This lets them read data beyond their own records, including other patients' demographics and users' password hashes.
Read the original description
OpenEMR before 8.5.0 contains an SQL injection vulnerability in the patient portal OnsiteDocument.Query endpoint, where mass-assigned _BitwiseAnd criteria parameters are placed unquoted into SQL with only quote-character escaping. Authenticated portal patients can inject SQL outside their per-patient scope to read the entire database, including other patients' demographics and users_secure password hashes.
Who should check
Teams running OpenEMR before 8.5.0 with the Patient Portal enabled, including patient-facing deployments.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.3/10CVSS 8.3
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Patient Portal enabled (portal_onsite_two_enable=1) OpenEMR 8.1.0 and earlier, per the advisory bodyUpgrade to a fixed version: 8.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126488 (OpenEMR before 8.5.0 SQL Injection via OnsiteDocument.Query _BitwiseAnd), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126488 (entry last updated 2026-11-13):
Affected:
- openemr openemr: fixed in 8.5.0
Fixed versions: 8.5.0.
Conditions (all must be true for the bug to be hit):
- Patient Portal enabled (portal_onsite_two_enable=1) (source: https://github.com/openemr/openemr/security/advisories/GHSA-g2xw-rvhq-x543)
- OpenEMR 8.1.0 and earlier, per the advisory body (source: https://github.com/openemr/openemr/security/advisories/GHSA-g2xw-rvhq-x543)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126488 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126488 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openemr/openemr/security/advisories/GHSA-g2xw-rvhq-x543
- https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-onsitedocument-query-bitwiseand
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126488
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126488"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.5.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126488
Is CVE-2026-126488 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in the OnsiteDocument.Query _BitwiseAnd handling lets an authenticated patient portal user send crafted requests that read the whole OpenEMR database. The advisory says this includes other patients' demographics and staff and admin password hashes.Source: github.com
Which versions are affected by CVE-2026-126488?
openemr: before 8.5.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory covers OpenEMR versions before 8.5.0, and names 8.1.0 and earlier as the affected releases. The setup involved is the Patient Portal being enabled with portal_onsite_two_enable=1, so check that setting and the installed OpenEMR version.Source: github.com
How do I fix CVE-2026-126488?
Upgrade OpenEMR to 8.5.0 or later, which is the listed fixed version. The facts give no separate vendor patch identifiers for this issue.Source: github.com