# CVE-2026-49142: OpenEMR Before 8.5.0 SQL Injection via form_icd_codes[]


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-4x43-68v3-4x7c, GHSA-w99c-jwcm-24hh

## What is CVE-2026-49142?

CVE-2026-49142 is a high-severity vulnerability in openemr, published on 29 Oct 2026. 

### Official description

OpenEMR before 8.5.0 contains an authenticated SQL injection vulnerability in the Syndromic Surveillance module that allows users with Clinician-level privileges to read and modify arbitrary database contents by submitting crafted values in the form_icd_codes[] POST parameter to the syndromicsurveillance/index endpoint. Attackers can inject an unquoted numeric IN() clause and UNION DISTINCT SELECT statement using hex-encoded literals to abuse MySQL extractvalue() for error-based exfiltration of bcrypt password hashes and execute stacked queries that reset passwords, resulting in full administrative account takeover.

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

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


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

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

## Is CVE-2026-49142 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-49142 is a high-severity vulnerability in openemr, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-49142 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-49142/ (Markdown: https://insights.sbomify.com/CVE-2026-49142/index.md)
```

## Sources

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

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