OpenEMR before 8.4.0 Missing Authorization via FHIR Media and QuestionnaireResponse Routes
Affects OpenEMR before 8.4.0 when a non-patient API token has the FHIR read scope but lacks the matching OpenEMR ACL. Fixed 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. OpenEMR versions before 8.4.0 (affected versions < 8.4.0). Non-patient API token (user or system token) that holds the FHIR read scope but lacks the corresponding OpenEMR 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 a missing authorization vulnerability in FHIR Media/:uuid and QuestionnaireResponse read routes that skip ACL checks. Non-patient API tokens lacking OpenEMR ACLs can request resources by uuid, bypassing compartment filtering to read any patient's documents and questionnaire responses.
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.
OpenEMR versions before 8.4.0 (affected versions < 8.4.0). Non-patient API token (user or system token) that holds the FHIR read scope but lacks the corresponding OpenEMR 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-124449
Is CVE-2026-124449 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 non-patient API token that has the FHIR read scope but lacks the matching OpenEMR ACL can read any patient's Media (documents and attachments) and QuestionnaireResponse records by uuid. This bypasses OpenEMR's ACL checks and compartment filtering.Source: github.com, vulncheck.com
Which versions are affected by CVE-2026-124449?
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, and the issue requires a non-patient user or system API token that holds the FHIR read scope without the corresponding ACL. Checking the installed OpenEMR version and the scopes granted to API tokens shows whether this setup is present.Source: github.com, vulncheck.com
How do I fix CVE-2026-124449?
Upgrade to OpenEMR 8.4.0, which contains the fix.Source: github.com, vulncheck.com