How severe is CVE-2026-24908?

CVE-2026-24908 has a CVSS 3.x base score of 9.9, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-24908 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-24908?

CVE-2026-24908 affects Open-emr Openemr. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-24908?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2026-24908 have an EU (EUVD) identifier?

Yes. CVE-2026-24908 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8703.

When was CVE-2026-24908 published?

CVE-2026-24908 was published on 2026-02-25 and last updated on 2026-06-17.

CVE-2026-24908

CVE-2026-24908 is a critical-severity vulnerability in Open-emr Openemr with a CVSS 3.x base score of 9.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Severity: Critical (CVSS 3.x base score 9.9)
EPSS exploit prediction: 0% (39th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-8703
Weakness: CWE-89
Affected product: Open-emr Openemr
Published: 2026-02-25
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-24908?: 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.
How severe is CVE-2026-24908?: CVE-2026-24908 has a CVSS 3.x base score of 9.9, rated critical severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-24908 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (39th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-24908?: CVE-2026-24908 affects Open-emr Openemr. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-24908?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-24908 have an EU (EUVD) identifier?: Yes. CVE-2026-24908 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-8703.
When was CVE-2026-24908 published?: CVE-2026-24908 was published on 2026-02-25 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*

More vulnerabilities in Open-emr Openemr

CVE-2026-24898 — Critical (CVSS 10.0): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
CVE-2026-24848 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. In 7.0.4 and…
CVE-2026-24849 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
CVE-2024-22611 — Critical (CVSS 9.8): OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php,…
CVE-2024-37734 — Critical (CVSS 9.8): An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid…
CVE-2020-13567 — Critical (CVSS 9.8): Multiple SQL injection vulnerabilities exist in phpGACL 3.3.7. A specially crafted HTTP request can lead to a SQL…

All CVEs affecting Open-emr Openemr →

Other CWE-89 (SQL Injection) vulnerabilities

CVE-2026-54350 — Critical (CVSS 10.0): Budibase is an open-source low-code platform. Prior to 3.39.12, an unauthenticated visitor of any published Budibase…
CVE-2026-8054 — Critical (CVSS 10.0): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in the Publish Audit API endpoints…
CVE-2026-42287 — Critical (CVSS 10.0): Emlog is an open source website building system. Prior to version 2.6.11, direct SQL injection in article creation and…
CVE-2026-3325 — Critical (CVSS 10.0): SQL injection (SQLi) in MegaCMS v12.0.0, specifically in the “id_territorio” parameter of the…
CVE-2025-10878 — Critical (CVSS 10.0): A SQL injection vulnerability exists in the login functionality of Fikir Odalari AdminPando 1.0.1 before 2026-01-26.…
CVE-2025-57792 — Critical (CVSS 10.0): Explorance Blue versions prior to 8.14.9 contain a SQL injection vulnerability caused by insufficient validation of…

Browse all CWE-89 (SQL Injection) vulnerabilities →