Vulnerability

OpenEMR Fax/SMS Module Access Control Bypass (CVE-2026-124450)

A broken-access-control and path-traversal flaw in OpenEMR, an open source electronic health record platform.

CVE ID
CVE-2026-124450
CVSS
9.9 Critical (CVSS v3.1, VulnCheck as CNA); 9.3 Critical (CVSS v4.0, VulnCheck, secondary); OpenEMR's own advisory lists the CVSS v4.0 score and does not publish a CVSS v3.1 vector
Affected product
OpenEMR, before 8.3.0, fax/sms module (oe-module-faxsms)
Exploited
Unknown
Published
8 November 2026 (CVE record and NVD); OpenEMR's advisory and the OpenEMR 8.3.0 fix were published 18 August 2026

In short

CVE-2026-124450 is a broken-access-control and path-traversal flaw in OpenEMR, an open source electronic health record platform. The flaw sits in the bundled fax/sms module, where the disposeDocument action for two fax-vendor clients never checks who is calling it. VulnCheck, the CNA, rates it CVSS 3.1 9.9 Critical, fixed in OpenEMR 8.3.0.

Profile MapVulnerability
  1. CVECVE-2026-124450
  2. ProductOpenEMR (open source project) OpenEMR, before 8.3.0, fax/sms module (oe-module-faxsms)
  3. Fix Steps5actions listedUpgrade to OpenEMR 8.3.0

What it allows

CVE-2026-124450 is a broken-access-control and path-traversal flaw in OpenEMR, an open source electronic health record platform. The flaw sits in the bundled fax/sms module, where the disposeDocument action for two fax-vendor clients never checks who is calling it. VulnCheck, the CNA, rates it CVSS 3.1 9.9 Critical.

The module's front controller checks only two things before it runs disposeDocument: that the action name is on an allow list, and that a valid CSRF token is present. Authentication is left to each fax vendor client's own code, and the advisory says two of the three fax vendor clients never run that check.

What CVE-2026-124450 Lets an Attacker Do

Without that check, the only barrier a caller meets is a weaker default permission. The advisory ties that permission to viewing patient demographics, not the stricter document-access permission a fax handler should require. The advisory says most clinical and clerical OpenEMR roles carry that weaker permission.

A user with only that permission can read sqlconf.php, the file that holds OpenEMR's database credentials, and can write files as the web server user, according to the CVE record. The record says this can enable remote code execution where the written file lands somewhere the web server will run it.

The advisory's author says they confirmed both the read and the write against OpenEMR's RingCentral fax client using a non-admin front-office account. The same missing checks exist in OpenEMR's SignalWire client too, which the advisory's author says they found by reviewing the code, not by testing it directly.

CVSS Score and CWE for CVE-2026-124450

VulnCheck scores CVE-2026-124450 as CVSS 3.1 9.9 Critical, with a secondary CVSS 4.0 score of 9.3 Critical. The CVE record lists CWE-73, external control of file name or path, as the primary weakness. See our CVSS entry for how to read the score.

What OpenEMR and CISA KEV Say About Exploitation

OpenEMR's advisory says 8.3.0 is the first fixed release, and every earlier release is affected. As of CISA's Known Exploited Vulnerabilities catalog version 2026.11.06, CVE-2026-124450 is not listed. The advisory and the CVE record do not state whether the flaw has been exploited.

Who is affected

The CVE record and OpenEMR's advisory both list every release before 8.3.0 as affected. OpenEMR 8.3.0 is the first patched release.

OpenEMR's advisory says the fix gives the RingCentral and SignalWire fax clients the same authentication and file-path checks the module's EtherFax client already had. GHSA-wf4w-mx2w-j4vv credits 4nt11 as the reporter.

We recommend planning the version upgrade with our vulnerability management guide. Our remote code execution entry explains why an arbitrary file write matters here.

OpenEMR 8.3.0 also fixes a second, narrower flaw we cover separately in the same module, CVE-2026-124490, which a different researcher reported specifically against the RingCentral client. Sites running the fax/sms module should patch for both.

Timeline

  1. 18 Aug 2026

    OpenEMR publishes the advisory GHSA-wf4w-mx2w-j4vv and OpenEMR 8.3.0, the first fixed release.

  2. 8 Nov 2026

    VulnCheck, the CNA, reserves and publishes CVE-2026-124450, and NVD publishes its entry the same day.

What to do

  1. Upgrade to OpenEMR 8.3.0

    The advisory and the CVE record list 8.3.0 as the first version that fixes CVE-2026-124450. This is a mandatory version change, not a configuration setting.

  2. Audit Who Can Reach the Fax/SMS Module

    Check which user roles carry the patients/demo permission the advisory says most clinical and clerical staff hold, and review the fax/sms module's own access settings separately.

  3. Disable the Fax/SMS Module Until You Upgrade

    If an immediate upgrade is not possible, disable the fax/sms module, or turn off the RingCentral and SignalWire vendors inside it, as a stopgap.

  4. Review Server Files for Unexpected Writes

    Check web-writable directories for files you did not put there, especially anywhere the web server can execute code, since the advisory says the write path can reach those locations.

  5. Protect the Database Credentials File

    We recommend confirming sqlconf.php and other configuration files stay unreadable from outside the application, and rotating database credentials if past exposure cannot be ruled out.

Questions

Which OpenEMR versions does CVE-2026-124450 affect?

The CVE record and OpenEMR's advisory both list every release before 8.3.0 as affected. OpenEMR 8.3.0 is the first fixed release.

What permission does an attacker need to exploit CVE-2026-124450?

The advisory ties the flaw to patients/demo, a broad viewing permission most clinical and clerical OpenEMR roles carry. No admin rights are needed, per the advisory.

Does CVE-2026-124450 affect OpenEMR's SignalWire fax client too?

The advisory's author says the SignalWire client has the same missing checks, found by reviewing its code rather than by testing it directly.

Can CVE-2026-124450 lead to remote code execution?

The CVE record says writing a file as the web server user can enable remote code execution where the written file lands somewhere the server will run it.

Is CVE-2026-124450 in the CISA KEV catalog?

It is not listed in catalog version 2026.11.06. The advisory and the CVE record do not state whether the flaw has been exploited.

Sources

  1. CVE-2026-124450 Record CVE Program / VulnCheck CNA
  2. CVE-2026-124450 NVD
  3. GHSA-wf4w-mx2w-j4vv, OpenEMR 8.2.0: authenticated arbitrary file read/write in the fax/sms module (disposeDocument) OpenEMR on GitHub
  4. OpenEMR before 8.3.0 Arbitrary File Read/Write via disposeDocument VulnCheck
  5. Known Exploited Vulnerabilities Catalog CISA