CVE
OpenEMR SQL injection in X12 835 ERA upload processing
Affects OpenEMR before 8.5.0 where the X12 835 (ERA) remittance upload feature is used by an account with billing permissions. 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. OpenEMR versions before 8.5.0. The X12 835 (ERA) remittance upload feature must be used. Attacker needs an account with billing permissions (acct/bill or acct/eob write), or a malicious payer ERA file uploaded by a clerk.
- 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.46% · 40th 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? →
- 17/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
OpenEMR, the electronic health records software, is affected by an SQL injection flaw in how it processes uploaded X12 835 ERA billing files. An attacker can reach it remotely with low-privilege login, such as a billing user, or through a malicious payer's ERA file that a clerk uploads, and then run arbitrary SQL to read any table, including password hashes, and modify data.
Read the original description
OpenEMR before 8.5.0 contains an SQL injection vulnerability in SLEOB::slInvoiceNumber() in src/Billing/SLEOB.php, which concatenates the CLP01 claim identifier from uploaded X12 835 ERA files into a query without escaping or parameter binding. Authenticated users with billing permissions, or a malicious payer whose ERA file a clerk uploads, can execute arbitrary SQL to read any table, including users_secure password hashes, and modify data.
Who should check
Teams running OpenEMR before 8.5.0 that use the billing ERA (X12 835) upload screen, such as billing clerks and practices receiving payer remittance files.
Read the source excerpt
“OpenEMR before 8.5.0 SQL Injection via CLP01 element of X12 835 ERA upload”
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.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenEMR versions before 8.5.0. The X12 835 (ERA) remittance upload feature must be used. Attacker needs an account with billing permissions (acct/bill or acct/eob write), or a malicious payer ERA file uploaded by a clerk.Upgrade 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-126482 (OpenEMR before 8.5.0 SQL Injection via CLP01 element of X12 835 ERA upload), 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-126482 (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):
- OpenEMR versions before 8.5.0. (source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-clp01-element-of-x12-835-era-upload)
- The X12 835 (ERA) remittance upload feature must be used. (source: https://github.com/openemr/openemr/security/advisories/GHSA-cw3f-mhw8-44jp)
- Attacker needs an account with billing permissions (acct/bill or acct/eob write), or a malicious payer ERA file uploaded by a clerk. (source: https://github.com/openemr/openemr/security/advisories/GHSA-cw3f-mhw8-44jp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126482 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126482 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-cw3f-mhw8-44jp
- https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-clp01-element-of-x12-835-era-upload
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-126482
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-126482"}.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-126482
Is CVE-2026-126482 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?
The CLP01 element of an X12 835 ERA upload is inserted into a SQL query without proper handling, which is an SQL injection flaw. The advisory says it allows full read of any table, including the users_secure password hashes and patient data, and modification of data.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126482?
openemr: before 8.5.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.5.0 are in range, but only where the X12 835 (ERA) remittance upload feature is used. The upload must come from an authenticated user with billing permissions (acct/bill or acct/eob write), or from a malicious payer ERA file uploaded by a clerk. Check the installed OpenEMR version and whether this upload feature is in use.Source: vulncheck.com, github.com
How do I fix CVE-2026-126482?
Upgrade OpenEMR to 8.5.0 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com, github.com