OpenEMR before 8.3.0 Arbitrary File Read/Write via oe-module-faxsms disposeDocument
Only OpenEMR before 8.3.0 with the oe-module-faxsms module enabled and RingCentral as the active fax or SMS vendor is affected. Fixed in 8.3.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OpenEMR versions before 8.3.0 are affected The oe-module-faxsms module must be enabled and configured by an administrator The active fax or SMS vendor must be RingCentral
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenEMR before 8.3.0 contains a path traversal vulnerability in the RingCentral RCFaxClient disposeDocument() method of oe-module-faxsms that allows authenticated attackers to read and write arbitrary files via the file_path parameter. Attackers can use action=download to read credentials and source code, or action=setup with base64 content to write web-executable files for code execution.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.4/10CVSS 9.4
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenEMR versions before 8.3.0 are affected The oe-module-faxsms module must be enabled and configured by an administrator The active fax or SMS vendor must be RingCentralUpgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- openemr openemr
fixed in 8.3.0
Evidence 2
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124490
Is CVE-2026-124490 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The disposeDocument function in the oe-module-faxsms module has a path traversal flaw. An authenticated user can use it to read sensitive server files, such as credentials and source code, and to write arbitrary files, which could lead to full system compromise.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124490?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 are in scope, but only when the oe-module-faxsms module is enabled and configured and the active fax or SMS vendor is RingCentral. To check, look up the OpenEMR version in the admin interface, then check whether the faxsms module is enabled and which vendor is set as active in its configuration.Source: vulncheck.com, github.com
How do I fix CVE-2026-124490?
Upgrade OpenEMR to version 8.3.0 or later, which contains the fix.Source: vulncheck.com, github.com