On this page (7 sections)
A critical vulnerability, tracked as CVE-2026-124450, affects OpenEMR versions before 8.3.0. According to the NVD record, a broken access control and path traversal weakness in the fax/sms module lets an authenticated, low-privilege user read the database configuration file and write arbitrary files on the server, which can lead to remote code execution.
If you run OpenEMR, host it for a clinic, or manage servers that do, this deserves prompt attention. The flaw needs only a low-privilege account rather than an administrator, and it exposes database credentials as well as allowing files to be written to the server.
What happened
The CVE was published on 2026-11-08. The description points to the disposeDocument action in OpenEMR's fax/sms module, where a file_path parameter is not validated. An attacker who already holds a low-privilege login can abuse this to reach files they should never touch.
The record names two outcomes. First, the attacker can read sqlconf.php, which the record describes as the source of database credentials. Second, the attacker can write arbitrary files as the web server user. Writing files that the web server will execute is the usual route from a file-write bug to remote code execution, and the record states that this flaw enables it.
Technical details in plain terms
Path traversal means an application builds a file location from user input without checking where it ends up. If the check is missing, the input can point to files outside the folder the developer intended. Here the unvalidated input is the file_path parameter of the disposeDocument action.
Two problems combine. The access control is too loose, so a low-privilege user can call a function that should not be available to them. The path handling is also too loose, so that function can read and write files wherever the web user has permission.
- Read impact: sqlconf.php yields database credentials, which could give an attacker access to the database behind the application, not just the web application itself.
- Write impact: arbitrary files written as the web user can be used to place code that the server runs.
- Privilege needed: an authenticated account with low privileges.
The research does not describe any attack steps, and this article does not either. What matters for defenders is that a minor account can become control of the application server plus a copy of the database credentials.
Who is affected
Any OpenEMR installation running a version earlier than 8.3.0 is in scope according to the CVE description. The research does not say whether the fax/sms module must be enabled or configured for the flaw to be reachable, so assume it is reachable until you have confirmed otherwise with the vendor advisory.
Exposure is likely to be higher when:
- The login page is open to the internet rather than restricted to a VPN or office network.
- Many users hold accounts, including temporary staff, former employees or shared logins, since any low-privilege account is enough.
- Database credentials are reused elsewhere, which would widen the impact of a leak.
How to check your exposure
First find out which version you run. Use whatever your deployment gives you, such as your package or deployment records, your upgrade history, or the instructions in the vendor advisory (GHSA-wf4w-mx2w-j4vv on the OpenEMR GitHub), and compare the result with 8.3.0. Anything earlier is listed as affected.
Then look for signs that the flaw was used. The research gives no indicators of compromise, so these are general checks. The command below is read-only: it searches your web server access logs for requests that mention disposeDocument. Adjust the log path to your setup (this example uses a common Debian/Ubuntu Apache location) and review any hits from accounts or IP addresses you do not recognize.
sudo grep -i "disposeDocument" /var/log/apache2/access.log*On RHEL-based systems the Apache log directory is usually different. This is the equivalent read-only search.
sudo grep -i "disposeDocument" /var/log/httpd/access_log*Legitimate use of the fax/sms module will also match, so a hit alone proves nothing. Look for requests with unusual file_path values, for example ones containing parent-directory sequences, and for activity from low-privilege users who have no reason to use faxing.
Also check for files you did not put there. This read-only command lists PHP files modified in the last 7 days under the OpenEMR directory. Replace the path with your own install location, and investigate any file you cannot explain.
sudo find /var/www/html/openemr -type f -mtime -7 -name "*.php"What to do now
- Confirm your OpenEMR version and plan an upgrade to 8.3.0 or later; the record lists only versions before 8.3.0 as affected, so confirm the exact fixed release in the vendor advisory.
- Take a full backup of the files and database before upgrading, and test the upgrade on a copy if you can.
- Read the vendor advisory (GHSA-wf4w-mx2w-j4vv on the OpenEMR GitHub) for exact fixed releases and any workarounds before you start.
- Until you have patched, restrict access to OpenEMR to a VPN or known IP ranges.
- Review the user list, remove unused or shared accounts, and make sure everyone has the minimum role they need.
- If you suspect misuse, rotate the database password stored in sqlconf.php and any other credentials that share it, and review database access logs.
- Check the install directory for unexpected files and review server logs for the patterns above.
- Where your setup allows it, make sure the web server user cannot write to application code directories, which limits what a file-write bug can achieve.
If you find evidence of compromise, treat the server as untrusted: preserve logs, isolate the host, and follow a recovery process such as Website hacked: what to do. If the system handles personal or health records, check your legal obligations for breach assessment and notification in your jurisdiction.
Detection and ongoing monitoring
Patching closes this specific hole, but the same pattern, a low-privilege account reaching sensitive files, is worth watching for over time. Keep access logs long enough to look back several weeks, alert on new script files appearing in the application directory, and review account creation and login activity regularly.
From the outside, you can check what your server exposes to the internet with the free website malware scanner and keep an eye on certificate and header changes with monitoring. These show what is visible from outside and do not replace patching or an internal review of the server. For background, read What outside-in malware detection can and cannot see.
A web application firewall can add a layer in front of an application, but it is not a substitute for the upgrade. See What is a WAF? for what it can and cannot do.
What is still unknown
- Whether the flaw is being exploited in the wild: the research reports no exploitation, and the CVE is not in CISA KEV, but absence of reports is not proof of safety.
- Which release the vendor names as the fix, since the record only lists versions before 8.3.0 as affected.
- Whether the fax/sms module must be enabled for the flaw to be reachable.
- Whether any official workaround exists short of upgrading.
- Which body assigned the CVSS 9.3 score; the research gives the score without naming one.
The OpenEMR GitHub advisory, the GitHub advisory entry and the VulnCheck advisory are the places to confirm these points. This article is worth rechecking against them as more details appear.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
