OpenEMR before 8.3.0 IDOR via OnsitePortalActivityController Update Endpoint
OpenEMR before 8.3.0 with the patient portal enabled lets an authenticated portal patient reach another patient's portal activity record if they can guess its ID. Fixed 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 version before 8.3.0 Patient portal enabled Attacker must know or enumerate another patient's portal activity id
- 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 an insecure direct object reference vulnerability in OnsitePortalActivityController::Update() that checks the request's patientId instead of the stored record's owner. Authenticated portal patients can send PUT requests to the onsiteportalactivity API with another patient's activity id and their own patientId to disclose tableArgs and checksum data, overwrite narratives and status, and take ownership of the record.
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 version before 8.3.0 Patient portal enabled Attacker must know or enumerate another patient's portal activity idUpgrade 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 3
- Advisory
- Advisory
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124447
Is CVE-2026-124447 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 patient on the portal can reach the update endpoint for another patient's portal activity record, because the server does not check that the record belongs to them. That lets them read the record's tableArgs and checksum data, overwrite its narratives and status, and take ownership of it.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-124447?
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 affected, and the patient portal must be enabled. The attacker needs to know or enumerate another patient's portal activity ID. To check your version, look at the OpenEMR version shown in the admin or footer area, and check whether the patient portal is enabled in the site settings.Source: vulncheck.com, github.com
How do I fix CVE-2026-124447?
Upgrade OpenEMR to 8.3.0 or later, which contains the fix.Source: vulncheck.com, github.com