CVE-2026-124450: Authenticated Arbitrary File Read/Write in OpenEMR FaxSMS disposeDocument
- Vendor
- Openemr
OpenEMR before 8.3.0 contains broken access control and unrestricted file-path handling in the FaxSMS module's RingCentral and SignalWire disposeDocument implementations. The handlers omit expected authentication checks and accept an attacker-controlled file_path without adequate document authorization, path containment, extension validation, or executable-content checks. An authenticated user with demographic-viewing permission can read files accessible to the web server account, including database configuration containing credentials, and write to attacker-selected locations permitted by that account. The download branch reads attacker-selected files and returns unencrypted input unchanged. The setup branch decodes supplied content and writes it to the selected destination. With drive encryption disabled, executable content can be written verbatim, enabling remote code execution where the destination is web-accessible and executable.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises filesystem confidentiality and integrity within the web server account's permissions. Database credential disclosure can enable access to application data, subject to database connectivity and credential privileges. Arbitrary writes can overwrite or corrupt accessible files and disrupt application operation. When drive encryption is disabled and a writable destination supports server-side execution, an attacker can execute code as the web server account. Enabling drive encryption does not eliminate arbitrary file reads or unchecked file overwrite and corruption.
Mitigation
If you can’t patch tonight, do this now.
Until the upgrade is completed, disable the affected FaxSMS functionality or restrict access to its disposeDocument action. No vendor workaround is specified. Drive encryption alone is insufficient because arbitrary reads and file overwrite or corruption remain possible.
Remediation
Patch, then assume compromise.
Upgrade OpenEMR to version 8.3.0 or later. Version 8.3.0 centralizes document handling across fax providers, requires patients/docs authorization, confines resolved paths to the configured temporary directory, and validates download targets. It restricts write extensions to pdf, tif, tiff, and txt, applies strict base64 decoding and executable-content checks, and uses an encrypted temporary-file write-and-rename flow with restrictive permissions. If compromise is suspected, investigate unauthorized file writes and rotate potentially exposed database credentials.
Exploits
1 exploit validated by Mallory's analysis.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-124450 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-124450?
- Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2026-124450, the earliest disclosed Nov 9, 2026.
- Is there a patch for CVE-2026-124450?
- Upgrade OpenEMR to version 8.3.0 or later. Version 8.3.0 centralizes document handling across fax providers, requires patients/docs authorization, confines resolved paths to the configured temporary directory, and validates download targets.
- What products are affected by CVE-2026-124450?
- Openemr.
- How severe is CVE-2026-124450?
- CVE-2026-124450 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.49% (43rd percentile) as of Nov 17, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.