OpenEMR before 8.4.0 Cross-Patient PHI Exfiltration via SMART Patient Launch
OpenEMR versions before 8.4.0 are affected when a SMART standalone-launch user holds only the patients|demo ACL. The fix is in 8.4.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.4.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected OpenEMR versions are those before 8.4.0. Attacker must be a SMART standalone-launch user holding 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? →
- 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.4.0 contains an authorization bypass allowing low-privileged SMART standalone-launch users to bind arbitrary patient UUIDs into the OAuth token context. Attackers with only the patients|demo ACL can select a victim during authorization and read that patient's clinical notes and documents through patient-scoped DocumentReference and Binary FHIR endpoints.
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.1/10CVSS 7.1
- 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.
Affected OpenEMR versions are those before 8.4.0. Attacker must be a SMART standalone-launch user holding the patients|demo ACL.Upgrade to a fixed version: 8.4.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.4.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-124482
Is CVE-2026-124482 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 SMART standalone-launch user with only the patients|demo ACL can read another patient's clinical note contents and downloadable patient documents. The attacker does this by selecting that victim during authorization.Source: github.com
Which versions are affected by CVE-2026-124482?
openemr: before 8.4.0.Source: cve.now feed data
Am I affected, and how do I check?
OpenEMR versions before 8.4.0 are affected, in setups where SMART standalone launch is used and the launching user holds the patients|demo ACL. To check, look at the OpenEMR version in the installation and the ACL assigned to SMART launch users.Source: github.com
How do I fix CVE-2026-124482?
Upgrade OpenEMR to 8.4.0 or later, which contains the fix.Source: github.com