Quick answers
- Is CVE-2026-124484 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124484 being exploited in the wild.
- How severe is CVE-2026-124484?
- High severity, with a CVSS score of 8.8, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.4.0.
- Is there a fix for CVE-2026-124484?
- Yes: fixed in 8.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124484 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-124484?
- 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.4.0
Technical details
A missing authorization vulnerability in OpenEMR's OnsiteDocumentController allows authenticated core users to bypass patient isolation checks by omitting or manipulating the patientId parameter. The portal bootstrap falls back to core mode for any session with authUserID, and the route map marks onsite-document endpoints with p_all permission but defers authorization checks to the controller, where patient filtering is driven by bootstrap_pid—leaving it empty when patientId is omitted. Attackers can fetch, read, update, and delete arbitrary patient portal documents by supplying arbitrary record IDs from a low-privileged front-office or administrative account.
Affected products
- OpenEMR OpenEMR before 8.4.0
Timeline
- 2026-11-08: disclosed