Quick answers
- Is CVE-2026-124483 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124483 being exploited in the wild.
- How severe is CVE-2026-124483?
- High severity, with a CVSS score of 8.3, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.4.0.
- Is there a fix for CVE-2026-124483?
- 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-124483 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-124483?
- 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
The prescription REST API routes (GET, POST, DELETE) check the patients.med ACL instead of the patients.rx ACL that governs prescription access elsewhere in the application. Because the authorization check does not request a specific permission bit, the ACL system accepts any allow-level access as sufficient, causing read-only Medical/History permissions to pass the authorization gate. Authenticated staff users can exploit this via the UI-exposed APICSRFTOKEN to enumerate prescription UUIDs, create active prescriptions for arbitrary patients, and deactivate existing prescriptions without per-patient or per-provider rebinding.
Affected products
- OpenEMR OpenEMR before 8.4.0
Timeline
- 2026-11-08: disclosed
- 2026-09-13: advisory: GitHub security advisory published