Quick answers
- Is CVE-2026-124471 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124471 being exploited in the wild.
- How severe is CVE-2026-124471?
- High severity, with a CVSS score of 8.1, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.3.0.
- Is there a fix for CVE-2026-124471?
- 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-124471 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-124471?
- 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 vulnerability is a missing authorization check (CWE-639) in interface/billing/sl_eob_invoice.php. The endpoint accepts an authenticated user's GET request with an encounter ID parameter and returns full billing and patient data without verifying ACL permissions or chart access rights. Attackers can enumerate encounter IDs to read billing notes and patient names, or POST form data (with a CSRF token rendered by the same endpoint) to modify payments, adjustments, and billing records.
Affected products
- OpenEMR OpenEMR before 8.3.0
Timeline
- 2026-08-18: disclosed: GitHub Security Advisory published
- 2026-11-08: advisory