OpenEMR before 8.3.0 Missing Authorization and IDOR via sl_eob_invoice.php
OpenEMR versions before 8.3.0 are affected, and any logged-in user account can reach billing data through sl_eob_invoice.php. 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 Attacker must hold any authenticated OpenEMR user account Default installation with no special setting
- 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 missing authorization vulnerability in interface/billing/sl_eob_invoice.php that allows any authenticated user to read and modify billing data for any encounter. Attackers can iterate the id parameter to read patient names and billing notes, and post payments, adjustments, deletions, or billing notes against any patient's account.
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
- Severity8.6/10CVSS 8.6
- 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 Attacker must hold any authenticated OpenEMR user account Default installation with no special settingUpgrade 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-124471
Is CVE-2026-124471 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 billing page sl_eob_invoice.php does not check that a logged-in user is authorized for the record it returns. By changing the id parameter, any authenticated user can view patient names and billing notes for other encounters, change billing notes, post fake payments and adjustments, and delete accounts receivable transactions.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124471?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.3.0 fall in the affected range, including default installations with no special setting. The precondition is holding any authenticated OpenEMR user account. Check the installed OpenEMR version against 8.3.0 to see which side of the range a given install is on.Source: vulncheck.com, github.com
How do I fix CVE-2026-124471?
Upgrade to OpenEMR 8.3.0 or later, which contains the fix.Source: vulncheck.com, github.com