OpenEMR SQL injection in Fee Sheet warehouse parameter
Affects OpenEMR before 8.3.0 for authenticated users whose role passes the fee_sheet ACL check, through the Fee Sheet warehouse field. Fixed in 8.3.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Summary
Written by a model
OpenEMR before 8.3.0 contains an SQL injection vulnerability in the Fee Sheet drug-inventory lookup (DrugSalesService::sellDrug) that interpolates the prod[N][warehouse] POST field into an ORDER BY clause. Low-privileged authenticated users can submit Fee Sheet product lines with constant subqueries to run a time-based blind oracle, extracting patient data and users_secure bcrypt hashes.
Who should check
Teams running OpenEMR before 8.3.0 with the Fee Sheet form, where clinical staff such as nurses can save product lines
“OpenEMR before 8.3.0 contains an SQL injection vulnerability in the Fee Sheet”
What to do
Check whether your setup matches what the bug needs.
OpenEMR before 8.3.0 with the Fee Sheet product line save path reachable via the prod[N][warehouse] POST field The attacker must be an authenticated user whose role passes the fee_sheet ACL checkUpgrade to a fixed version: 8.3.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-124469 (OpenEMR before 8.3.0 SQL Injection via Fee Sheet warehouse parameter), 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-124469 (entry last updated 2026-11-10):
Affected:
- openemr openemr: fixed in 8.3.0
Fixed versions: 8.3.0.
Conditions (all must be true for the bug to be hit):
- OpenEMR before 8.3.0 with the Fee Sheet product line save path reachable via the prod[N][warehouse] POST field (source: https://github.com/openemr/openemr/security/advisories/GHSA-cg8c-2v5q-29g7)
- The attacker must be an authenticated user whose role passes the fee_sheet ACL check (source: https://github.com/openemr/openemr/security/advisories/GHSA-cg8c-2v5q-29g7)
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-124469 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124469 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-cg8c-2v5q-29g7
- https://www.vulncheck.com/advisories/openemr-before-8.3.0-sql-injection-via-fee-sheet-warehouse-parameter
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-124469
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-124469"}.Affected versions
- openemr openemrfixed in 8.3.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.4, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 25 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now2 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Public exploit activity
- EPSS: 0.47%
- Posted on X by cve.now Nov 8
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · openemr/openemr · Advisory GHSA-cg8c-2v5q-29g7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-124469 |
| Record | NVD · CVE-2026-124469 |
| Other links 1 | |
| Link | vulncheck.com · advisories/openemr-before-8.3.0-sql-injection-via-fee-sheet-warehouse-parameter |
Questions about CVE-2026-124469
Is CVE-2026-124469 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 Fee Sheet save path does not safely handle the warehouse value sent in the per-product POST field, so SQL can be injected through it. The advisory says this lets a low-privileged clinical role read the whole OpenEMR database using blind timing, including patient data and bcrypt password hashes for admin and provider accounts.
Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124469?
openemr: before 8.3.0.
Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 are affected where the Fee Sheet product line save path is reachable through the prod[N][warehouse] POST field. The attacker must be an authenticated user whose role passes aclCheckForm('fee_sheet'). To check an installation, compare its OpenEMR version with 8.3.0 and review which roles hold the fee_sheet ACL permission.
Source: github.com, vulncheck.com
How do I fix CVE-2026-124469?
Upgrade OpenEMR to version 8.3.0 or later, which is the listed fixed version. The facts name no separate patch IDs or workaround.
Source: github.com, vulncheck.com
Related
- CVE-2026-126322OpenEMR before 8.3.0 Unsanitized Deserialization via patient_match_dialog.php
- CVE-2026-126430OpenEMR before 8.5.0 SQL Injection via CCR revandapprove Field Names
- CVE-2026-126428OpenEMR before 8.5.0 RCE via Stored ERA Upload and Background Services
- CVE-2026-126431OpenEMR before 8.5.0 Second-Order SQL Injection via Carecoordination CCDA Mapper
- CVE-2026-126415OpenEMR before 8.5.0 Missing Authorization via Patientvalidation Module
- CVE-2026-126416OpenEMR before 8.5.0 Improper Authorization via patient_tracker_status.php
No corrections so far. Something wrong on this page? Report an error.