CVE-2026-126480: openemr · SQL Injection
Affects openemrSource CVE Database V5
Not known to be exploited · CVSS 8.6 High : upgrade to 8.5.0 soon.
Data as of 13 Nov 2026, 10:44 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 8.6 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 8.1 |
- Patch
- Available – fixed in 8.5.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| openemropenemr | Affected
| Fixed in
|
AI-suggested
Upgrade OpenEMR to version 8.5.0 or later, where this vulnerability is fixed. Since the vulnerability requires authentication and exploits a route lacking access control and CSRF protections, applying the official patch is the recommended remediation. No additional mitigations are specified by the vendor advisory.
Description
OpenEMR versions prior to 8.5.0 contain an SQL injection vulnerability in the CcrTable::insertApprovedData() function. Authenticated users can exploit this flaw by injecting SQL through specially crafted request parameter names used as column names. The vulnerability exists because the revandapprove route lacks access control and CSRF protections, allowing attackers to manipulate patient data fields, including copying password hashes or corrupting records. This issue was fixed in version 8.5.0.