OpenEMR before 8.3.0 Path Traversal via sl_eob_process.php eraname
Affects OpenEMR before 8.3.0 when the eraname parameter of the ERA/EOB processor page sl_eob_process.php is supplied. The fix is 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 Affects the ERA/EOB processor interface/billing/sl_eob_process.php when the eraname parameter is supplied
- 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? →
- 15/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 interface/billing/sl_eob_process.php that allows authenticated users to write and read files by supplying unsanitized eraname values. Attackers without billing privileges can inject ../ sequences to create ERA report .html files anywhere the web user can write and parse arbitrary .edi files echoed into the report.
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
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 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 Affects the ERA/EOB processor interface/billing/sl_eob_process.php when the eraname parameter is suppliedUpgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen 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-124457
Is CVE-2026-124457 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?
An authenticated user without billing privileges can use the eraname parameter to write .html files to any location the web server user can write to. The same user can also read and parse arbitrary .edi files, and their contents are echoed into the report.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124457?
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 the affected range. The issue concerns the ERA/EOB processor at interface/billing/sl_eob_process.php when the eraname parameter is supplied. Check the installed OpenEMR version to see whether it falls below 8.3.0.Source: vulncheck.com, github.com
How do I fix CVE-2026-124457?
Upgrade OpenEMR to 8.3.0 or later, which is the fixed version.Source: vulncheck.com, github.com