CVE-2026-24908 OpenEMR has SQL Injection in Patient API Sort Parameter
Authenticated attackers can execute arbitrary SQL queries via the Patient API sort parameter, exposing PHI and credentials in OpenEMR.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-24908?
CVE-2026-24908 is a critical SQL injection vulnerability in Open-Emr Openemr, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-89
Which versions are affected by CVE-2026-24908?
It affects 1 product.
Products include Open-Emr Openemr.
How do I fix CVE-2026-24908?
No fix has been published for CVE-2026-24908 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-24908 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24908 exists.
Other vulnerabilities in Open-Emr Openemr
Sources
Also known as GHSA-rcc2-45v3-qmqm.