Back to CVE records
Critical 10.0HealthcarePublished Feb 25, 2026

CVE-2026-24908OpenEMR has SQL Injection in Patient API Sort Parameter

Updated under an hour ago ()

Does this affect you?

It affects openemr and 1 other product. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.51%, higher than 42% of scored CVEs.

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0, an SQL injection vulnerability in the Patient REST API endpoint allows authenticated users with API access to execute arbitrary SQL queries through the `_sort` parameter. This could potentially lead to database access, PHI (Protected Health Information) exposure, and credential compromise. The issue occurs when user-supplied sort field names are used in ORDER BY clauses without proper validation or identifier escaping. Version 8.0.0 fixes the issue.

CVSS
10.0 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weakness (CWE)
CWE-89
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
0.51% (percentile 42)
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Feb 26, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
openemr openemr
openemr:openemr (from the name)
before 8.0.0
CNA record
open-emr openemr
open-emr:openemr
before 8.0.0
NVD

References

  • x-refsource-confirm, exploit, vendor-advisory
  • x-refsource-misc, patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.