Skip to main content
VulnerabilityPublished

CVE-2026-126488: openemr · SQL Injection

Affects openemrSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 8.5.0 soon.

Data as of 13 Nov 2026, 10:42 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.3
CNA (VulnCheck)CVSS 3.17.7
Patch
Available – fixed in 8.5.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade openemr to 8.5.0.

Affected software

ProductAffectedFixed in
openemropenemrAffected
  • <8.5.0
Fixed in
  • 8.5.0

AI-suggested

Upgrade OpenEMR to version 8.5.0 or later, where this SQL injection vulnerability is fixed. No other mitigations are indicated or required according to the available data.

Description

OpenEMR versions prior to 8.5.0 contain an SQL injection vulnerability in the patient portal's OnsiteDocument.Query endpoint. This flaw allows authenticated patients to inject SQL commands beyond their own data scope, potentially exposing the entire database including other patients' demographic information and password hashes. The vulnerability arises from improper neutralization of special elements in SQL commands, specifically with mass-assigned _BitwiseAnd criteria parameters that are only escaped for quote characters but not properly quoted. The issue is fixed in OpenEMR version 8.5.0.

References

Community reviews

Loading reviews…