# CVE-2026-124490: OpenEMR path traversal in oe-module-faxsms disposeDocument

Source: https://junglewise.ai/threats/cve-2026-124490-openemr-before-8-3-0-contains-a-path-traversal-vulnerability-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-124490 · Severity: critical · CVSS 9.1 · Published 2026-11-08

OpenEMR is an open-source electronic health records and practice management system used by healthcare providers. A flaw in its fax/SMS module allows authenticated users to read sensitive server files (such as database credentials and source code) or write malicious files to the server, potentially enabling a complete system takeover. This affects healthcare organizations using the RingCentral fax integration.

Technologies: [OpenEMR](https://junglewise.ai/threats/technologies/openemr-openemr). Vendors: [OpenEMR](https://junglewise.ai/threats/vendors/openemr).

## Quick answers

**Is CVE-2026-124490 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-124490 being exploited in the wild.

**How severe is CVE-2026-124490?** Critical severity, with a CVSS score of 9.1, published 8 November 2026.

**Which products and versions are affected?** OpenEMR before 8.3.0.

**Is there a fix for CVE-2026-124490?** Yes: fixed in 8.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-124490 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-124490?** Check whether you run OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 8.3.0

## Technical details

The RCFaxClient disposeDocument() method in oe-module-faxsms fails to validate the file_path parameter, allowing path traversal attacks. Authenticated attackers can exploit action=download to read arbitrary files via readfile(), or action=setup to write arbitrary files via file_put_contents() using base64-encoded content. The method lacks both path restrictions and proper authorization checks despite a sibling method having been previously hardened.

## Affected products

- OpenEMR OpenEMR before 8.3.0

## Timeline

- 2026-08-18: disclosed
- 2026-11-08: advisory

## References

- [https://github.com/openemr/openemr/security/advisories/GHSA-38jw-pwgq-9hpj](https://github.com/openemr/openemr/security/advisories/GHSA-38jw-pwgq-9hpj)
- [https://www.vulncheck.com/advisories/openemr-before-8.3.0-arbitrary-file-read-write-via-oe-module-faxsms-disposedocument](https://www.vulncheck.com/advisories/openemr-before-8.3.0-arbitrary-file-read-write-via-oe-module-faxsms-disposedocument)

## Related threats

- [OpenEMR broken access control in portal payment processing](https://junglewise.ai/threats/cve-2026-124489-openemr-before-8-3-0-contains-a-broken-access-control)
- [OpenEMR authorization bypass in encounter form loaders](https://junglewise.ai/threats/cve-2026-124488-openemr-before-8-3-0-contains-an-authorization-bypass)
- [OpenEMR improper authorization in FHIR DocumentReference $docref](https://junglewise.ai/threats/cve-2026-124487-openemr-before-8-4-0-contains-an-improper-authorization)
- [OpenEMR missing authorization in classic document controller](https://junglewise.ai/threats/cve-2026-124486-openemr-before-8-3-0-contains-a-missing-authorization)
- [OpenEMR authorization bypass in patient portal onsitedocuments API](https://junglewise.ai/threats/cve-2026-124485-openemr-before-8-3-0-contains-an-authorization-bypass)