OpenEMR before 8.3.0 Arbitrary File Read/Write via disposeDocument
Affects OpenEMR before 8.3.0 when the fax/sms module is installed and active with a RingCentral or SignalWire fax vendor. 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. The fax/sms module (oe-module-faxsms) is installed and active. The fax vendor is RingCentral or SignalWire. The attacker holds a user role with the patients/demo ACL.
- 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 broken access control and path traversal vulnerability in the fax/sms module disposeDocument action via an unvalidated file_path parameter. Authenticated low-privilege users can read sqlconf.php to recover database credentials and write arbitrary files as the web user, enabling remote 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.3/10CVSS 9.3
- 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.
The fax/sms module (oe-module-faxsms) is installed and active. The fax vendor is RingCentral or SignalWire. The attacker holds a user role with the patients/demo ACL.Upgrade 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-124450
Is CVE-2026-124450 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?
A logged-in user whose role has the patients/demo permission can read files the web server user can access, such as sites/default/sqlconf.php, which holds database credentials. The same user can also write arbitrary files as the web server user, which the advisory says can enable remote code execution.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124450?
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 affected when the fax/sms module (oe-module-faxsms) is installed and active, which can be checked under Modules > Manage Modules, and the fax vendor is RingCentral or SignalWire (the setting oefax_enable_fax=6 routes to SignalWireClient). The vulnerable path requires a user role that has patients/demo.Source: github.com, vulncheck.com
How do I fix CVE-2026-124450?
Upgrade OpenEMR to version 8.3.0 or later. No workaround is listed in the facts.Source: github.com, vulncheck.com