Quick answers
- Is CVE-2026-124485 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124485 being exploited in the wild.
- How severe is CVE-2026-124485?
- Medium severity, with a CVSS score of 6.5, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.3.0.
- Is there a fix for CVE-2026-124485?
- Yes: fixed in 8.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124485 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-124485?
- Check whether you run OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 8.3.0
Technical details
The onsitedocuments API in the patient portal fails to properly validate query criteria parameters; while the bootstrap layer blocks direct pid and patientId tampering, an attacker can send empty pid_Equals and denialReason_IsNotLike parameters that are copied into the criteria object, bypassing both patient scoping and locked-document filters. An authenticated patient can exploit this via a GET request to /portal/patient/api/onsitedocuments to retrieve all matching onsite consent artifacts across patients. The fix is to validate and restrict criteria parameters server-side rather than allowing arbitrary parameter reflection.
Affected products
- OpenEMR OpenEMR before 8.3.0
Timeline
- 2026-08-18: disclosed: GitHub Security Advisory published
- 2026-11-08: advisory: NVD entry published