---
id: "CVE-2026-126425"
page: "https://infrastack.ai/live/CVE-2026-126425"
kind: "vulnerability"
aliases: ["CVE-2026-126425"]
title: "OpenEMR: stored SQL injection through history layout fields lets users read data"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["healthcare", "openemr", "runtime", "self-hosted", "sql"]
not_affected_if: ["no-write-access-users", "openemr-8.5.0-or-later"]
published_at: "2026-11-13T10:17:48+00:00"
first_seen_at: "2026-11-13T10:47:21+00:00"
updated_at: "2026-11-13T10:52:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126425", "first_seen_at": "2026-11-13T10:47:21+00:00"}]
exploit_sources: []
---

# OpenEMR: stored SQL injection through history layout fields lets users read data

Link for people: https://infrastack.ai/live/CVE-2026-126425 (this .md is for agents)

OpenEMR before 8.5.0 places unvalidated History layout field identifiers into an INSERT statement for patients without a history row. Users with admin or med write access can trigger SQL functions such as SLEEP, tying up database workers or reading data beyond their privileges.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the OpenEMR version in the installed application; versions before `8.5.0` are named as affected.
- Review who holds admin, super or patients/med write access in OpenEMR.

## Fix

- OpenEMR: move to `8.5.0` or later.

## Timeline

- 2026-11-13T10:47:21+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126425

## Documents

- [advisory] Vendor advisory: github.com https://github.com/openemr/openemr/security/advisories/GHSA-fq58-jp5g-x44q
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/openemr-before-8.5.0-stored-sql-injection-via-history-layout-field-identifiers

## From the sources

OpenEMR before 8.5.0 contains a stored SQL injection vulnerability in which History layout field identifiers saved through edit_layout.php, including HIS fields and LBF source-H fields, are placed unvalidated into an INSERT statement for patients without a history_data row. Users with admin/super and patients/med write access can trigger history_save.php or LBF saves to execute SQL functions like SLEEP, tying up database workers or accessing data beyond their privileges.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_