# CVE-2026-124469: OpenEMR before 8.3.0 SQL Injection via Fee Sheet warehouse parameter


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-cg8c-2v5q-29g7, GHSA-v2w6-cjv6-3m3w

## What is CVE-2026-124469?

CVE-2026-124469 is a critical vulnerability in openemr, published on 8 Nov 2026. 

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-124469?


## How do I fix CVE-2026-124469?

No fix has been published for CVE-2026-124469 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124469 being exploited?

There is no known exploitation of CVE-2026-124469 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124469 and fix it if it is affected.

What it is: CVE-2026-124469 is a critical vulnerability in openemr, published on 8 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124469 in the wild and no public exploit code.

Affected product: openemr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124469/ (Markdown: https://insights.sbomify.com/CVE-2026-124469/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124469
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124469
- OSV: https://osv.dev/vulnerability/CVE-2026-124469

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124469/
Summaries are generated and may contain mistakes; the official description above is the record.