Quick answers
- Is CVE-2026-124473 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124473 being exploited in the wild.
- How severe is CVE-2026-124473?
- High severity, with a CVSS score of 7.1, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.3.0.
- Is there a fix for CVE-2026-124473?
- 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-124473 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-124473?
- 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 SOAP note update API endpoint (/api/patient/:pid/encounter/:eid/soap_note/:sid) performs an SQL UPDATE on form_soap using only the note ID without verifying that the supplied sid belongs to the supplied patient (pid) and encounter (eid). An authenticated attacker with encounters|notes permission can craft PUT requests with another patient's note ID to overwrite clinical content and change the note's patient ownership. The read path correctly enforces patient and encounter binding, but the update path lacks this object-level authorization check.
Affected products
- OpenEMR OpenEMR before 8.3.0
Timeline
- 2026-08-18: disclosed
- 2026-11-08: advisory