CVE-2026-32127
SQL Injection in OpenEMR Ajax Graphs Library Allows Data Manipulation
Publication date: 2026-03-11
Last updated on: 2026-03-13
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| open-emr | openemr | to 8.0.0.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-32127 is a high-severity SQL injection vulnerability found in OpenEMR versions prior to 8.0.0.1, specifically in the ajax graphs library.'}, {'type': 'paragraph', 'content': "The vulnerability occurs because the library directly inserts user-supplied input from the 'name' parameter into SQL queries without proper sanitization or escaping of special SQL characters."}, {'type': 'paragraph', 'content': 'Authenticated attackers can exploit this flaw by injecting arbitrary SQL code, which allows them to access or manipulate sensitive data in the database.'}, {'type': 'paragraph', 'content': 'Proof-of-concept exploits demonstrate techniques such as time-based and boolean-based SQL injection to extract sensitive information like usernames and hashed passwords.'}, {'type': 'paragraph', 'content': 'This vulnerability is fixed in OpenEMR version 8.0.0.1.'}] [1]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive medical and user data stored in OpenEMR.
Attackers can manipulate or extract confidential information such as usernames, hashed passwords, and potentially other protected health information.
The impact includes potential data breaches, loss of data integrity, and disruption of availability.
In some cases, exploitation may lead to server-side code execution and full database compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by testing for SQL injection in the ajax graphs library of OpenEMR, specifically targeting the `name` parameter in POST requests to the file `library/ajax/graphs.php`.'}, {'type': 'paragraph', 'content': 'Proof-of-concept exploits use time-based and boolean-based SQL injection techniques. For example, injecting payloads like `date,SLEEP(5)` in the `name` parameter causes a delay, confirming the vulnerability.'}, {'type': 'paragraph', 'content': 'To detect the vulnerability, you can send authenticated POST requests to the vulnerable endpoint with crafted payloads in the `name` parameter and observe the response time or returned data.'}, {'type': 'list_item', 'content': 'Use curl or similar tools to send POST requests with payloads such as `name=date,SLEEP(5)` to observe time delays.'}, {'type': 'list_item', 'content': 'Example curl command: `curl -X POST -d "name=date,SLEEP(5)" -b cookies.txt https://<openemr-host>/library/ajax/graphs.php` (assuming you have authenticated cookies).'}, {'type': 'list_item', 'content': 'Monitor response times to detect time-based SQL injection.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade OpenEMR to version 8.0.0.1 or later, where this SQL injection vulnerability in the ajax graphs library has been fixed.
Until the upgrade can be performed, restrict authenticated user access to the vulnerable ajax graphs functionality to trusted users only.
Additionally, monitor logs for suspicious POST requests to `library/ajax/graphs.php` and consider implementing web application firewall (WAF) rules to detect and block SQL injection attempts targeting the `name` parameter.