On this page (7 sections)

A critical vulnerability, CVE-2026-124490, has been published for OpenEMR, the open-source electronic health records and practice management application. According to the GitHub Advisory Database entry, the fax and SMS module (oe-module-faxsms) in versions before 8.3.0 has a path traversal flaw that lets an authenticated user read and write arbitrary files on the server.

If you host or administer an OpenEMR instance, especially one reachable from the internet with the fax/SMS module in use, this deserves prompt attention. Writing files that the web server can execute turns a file access bug into code execution.

What happened

The flaw sits in the disposeDocument() method of the RingCentral RCFaxClient class inside the oe-module-faxsms module. The NVD record describes it as a path traversal that lets authenticated attackers read and write arbitrary files through the file_path parameter. The record was published on November 8, 2026.

Only one independent publisher covers this story so far. The NVD entry repeats the GitHub advisory text, so it is not separate confirmation. Related references include a project security advisory and a VulnCheck advisory, which we could not review in detail here.

Technical details

Path traversal happens when an application builds a file location from user-supplied input without confining it to an intended directory. By supplying a crafted path, a user can reach files elsewhere on the disk. Here, the advisory says the file_path parameter is the entry point.

The advisory describes two impacts:

  • Reading files: using the download action, an attacker can read credentials and source code.
  • Writing files: using the setup action with base64-encoded content, an attacker can write web-executable files, which leads to code execution.

The CVSS v4 metrics listed show a network attack vector, low attack complexity, no user interaction and high privileges required, with high impact on confidentiality, integrity and availability for both the vulnerable and subsequent systems. The high privileges requirement is important: the attacker needs a valid account with meaningful access first. That lowers the risk compared with an anonymous flaw, but stolen, reused or weak credentials, or a malicious insider, are all realistic ways to meet that condition.

The sources do not say which OpenEMR role is needed, whether the module is enabled by default, or whether a proof of concept exists. Treat those points as unknown.

Who is affected

Any OpenEMR installation older than 8.3.0 is in scope according to the advisory text. Exposure is highest when:

  • the oe-module-faxsms module is installed and enabled, particularly with RingCentral fax configured;
  • the application is reachable from the public internet rather than only through a VPN;
  • user accounts are shared, weakly protected or lack multi-factor authentication;
  • the web server user can write to directories that PHP will execute.

OpenEMR stores patient health information, so a successful file read could expose database credentials and configuration, and code execution could expose the records themselves. Regulatory obligations may apply if you suspect access; check with your compliance contact.

How to check your exposure

Start by finding your OpenEMR version. The admin interface typically shows it in the About or version information area. If you have shell access, you can also look at the version file in the application directory (the path depends on your installation).

This read-only command searches for the faxsms module directory under /var/www. Adjust the path to your web root; if it prints a path, the module is present on disk.

Search for the faxsms module directory in your OpenEMR install (run on the server)Shell
find /var/www -type d -name 'oe-module-faxsms' 2>/dev/null

Whether the module is enabled is shown in OpenEMR's module management screen. Next, look for signs of abuse in your web server access logs, such as requests to the fax/SMS module that include unusual file_path values or path sequences like ../. This read-only command filters Apache logs on Debian/Ubuntu for such requests.

Search Apache access logs for traversal sequences in faxsms requests (Debian/Ubuntu, read-only)Shell
grep -i 'faxsms' /var/log/apache2/access.log* | grep -E 'file_path=.*(\.\./|%2e%2e)'

On RHEL-style systems the Apache logs are usually under /var/log/httpd/, and nginx logs under /var/log/nginx/; point the same command at those files. A match is not proof of compromise, but it warrants a closer look. Also check for unexpected recently created PHP files. This read-only command lists PHP files modified in the last 7 days; unfamiliar entries in upload or document directories deserve scrutiny.

List PHP files modified in the last 7 days under the web root (read-only; adjust the path)Shell
find /var/www -type f -name '*.php' -mtime -7 -ls

What to do now

The advisory describes versions before 8.3.0 as affected, so upgrading to 8.3.0 or later is the primary fix. Because the GitHub entry lists patched versions as unknown, confirm the fixed release in the project's own security advisory before you rely on it.

Caution. Back up your files and database before upgrading, and test on a staging copy where you can. Upgrades can interrupt a clinical or booking system, so schedule them outside working hours.
  1. Identify every OpenEMR instance you run and record its version.
  2. Read the OpenEMR security advisory to confirm the fixed version and upgrade notes.
  3. Upgrade to OpenEMR 8.3.0 or later after taking a backup.
  4. If you cannot upgrade immediately, disable the oe-module-faxsms module and restrict access to OpenEMR to a VPN or trusted IP ranges.
  5. Review user accounts: remove unused ones, enforce strong unique passwords and enable multi-factor authentication where available.
  6. Check logs and the web root for suspicious requests and new or changed PHP files (see the commands above).
  7. If you find signs of compromise, rotate database and integration credentials, including any RingCentral keys, and follow an incident response process.

Disabling the module is our suggested interim measure, not one stated in the advisory, so confirm it does not break fax workflows you rely on. For broader guidance on handling a suspected breach, see Website hacked: what to do.

Detection and monitoring

After patching, keep watching for file changes and odd requests. Useful signals include new PHP files in upload or document directories, requests to module endpoints containing encoded traversal sequences, and logins from unfamiliar locations. A web application firewall can add a layer of filtering for traversal patterns, though it is not a substitute for patching; see What is a WAF? for what it can and cannot do.

You can also run a read-only Webforta security scan of a site you verify to review its publicly visible configuration. It is a general check, not a test for this specific flaw.

Timeline

The only date given in the sources is November 8, 2026, when CVE-2026-124490 was published to the National Vulnerability Database and the GitHub Advisory Database. The sources do not report any exploitation or a patch release date.

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.

  1. CVE-2026-124490 - GitHub Advisory Databasegithub.com
  2. CVE-2026-124490: OpenEMR before 8.3.0 contains a path traversal vulnerability in the RingCentral RCFaxClient disposeDocument() method of oe-module-faxsms that allows…nvd.nist.gov ·
  • OpenEMR
  • CVE-2026-124490
  • path traversal
  • healthcare
  • web application security