Security readout for executives and security teams
Plain-English summary
CVE-2026-24908 is a critical SQL injection flaw in OpenEMR before 8.0.0. An authenticated user with API access could abuse a Patient API sorting parameter to run unintended database queries. For healthcare organizations, the main concern is exposure of protected health information, possible credential compromise, and disruption to clinical systems.
Executive priority
Treat as urgent for any OpenEMR environment handling patient data. Prioritize upgrade planning, API access review, and monitoring because the vulnerability directly threatens PHI confidentiality and database integrity. No public active exploitation is confirmed in the provided sources.
Technical view
OpenEMR Patient REST API handling used user-supplied sort field names in SQL ORDER BY clauses without sufficient validation or identifier escaping. The vulnerability affects OpenEMR versions before 8.0.0 and is classified as CWE-89. The published CVSS 3.1 score is 10.0 with network access, low complexity, low privileges, and no user interaction.
Likely exposure
Exposure is limited to OpenEMR deployments before 8.0.0 where users or integrations have authenticated API access to the Patient REST API. Internet-facing API deployments, third-party integrations, and broadly provisioned API accounts increase business risk.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires authenticated API access, but successful abuse could affect confidentiality, integrity, and availability of the database, including PHI and credentials.
Researcher notes
The fix is referenced in OpenEMR commit 943e23cad6e979f87cdf168807fce2a7b32dd194 and the GitHub Security Advisory GHSA-rcc2-45v3-qmqm. Sources identify the vulnerable input as the Patient API `_sort` parameter, but validation should avoid unsafe testing against production patient data.
Mitigation direction
- Upgrade OpenEMR to version 8.0.0 or later.
- Review the GitHub advisory and vendor release guidance.
- Restrict Patient API access to required users and integrations.
- Reduce overly broad API privileges where operationally possible.
- Monitor database and API logs for unusual authenticated activity.
Validation and detection
- Inventory OpenEMR instances and confirm installed versions.
- Identify any OpenEMR deployment below version 8.0.0.
- Review which users and integrations have API access.
- Check whether the Patient REST API is exposed externally.
- Look for abnormal API sorting requests or database errors in logs.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24908 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H3.16Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
10CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/openemr/openemr/security/advisories/GHSA-rcc2-45v3-qmqmCVE reference · x_refsource_CONFIRM
- https://github.com/openemr/openemr/commit/943e23cad6e979f87cdf168807fce2a7b32dd194CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.