OpenEMR before 8.4.0 Improper Authorization via Prescription REST API
Affects OpenEMR before 8.4.0, where staff with only Medical/History view access (patients.med) can use the prescription API through the Local API bridge. Fixed in 8.4.0. No vendor rating is given.
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 The user holds only Medical/History view access (patients.med), with no prescription permission The Local API bridge is used, with the APICSRFTOKEN header taken from the main UI
- 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.4.0 contains an incorrect authorization vulnerability because the prescription REST API routes check the patients.med ACL instead of patients.rx and request no specific permission bit, so read-only Medical/History access passes the check. Authenticated staff users can reuse the UI-exposed APICSRFTOKEN to enumerate prescription UUIDs, forge prescriptions for arbitrary patients, and deactivate existing prescriptions tenant-wide.
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.7/10CVSS 8.7
- 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.4.0 The user holds only Medical/History view access (patients.med), with no prescription permission The Local API bridge is used, with the APICSRFTOKEN header taken from the main UIUpgrade 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-124483
Is CVE-2026-124483 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 staff user with only Medical/History view access can use the prescription REST API, which should require prescription permission. The flaw lets that user list prescription UUIDs, create prescriptions for arbitrary patients, and deactivate existing prescriptions across the installation.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124483?
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. The issue applies to users who hold patients.med access but no prescription permission, when the Local API bridge is used with the APICSRFTOKEN taken from the main UI. Compare the installed OpenEMR version with the 8.4.0 boundary to see which side of it a deployment falls on.Source: vulncheck.com, github.com
How do I fix CVE-2026-124483?
Upgrade to OpenEMR 8.4.0 or later, which contains the fix. The facts give no workaround for versions before 8.4.0.Source: vulncheck.com, github.com