Quick answers
- Is CVE-2026-124489 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124489 being exploited in the wild.
- How severe is CVE-2026-124489?
- 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-124489?
- Yes: fixed in 8.3.0. Until then: Restrict access to the portal payment page at /portal/portal_payment.php to portal sessions only, and enforce billing ACL checks (acct/bill or acct/eob write permissions) for all core user access before allowing patient context modification. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124489 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-124489?
- 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
Restrict access to the portal payment page at /portal/portal_payment.php to portal sessions only, and enforce billing ACL checks (acct/bill or acct/eob write permissions) for all core user access before allowing patient context modification.
Technical details
The vulnerability is a broken access control flaw in portal/portal_payment.php that accepts user-controlled patient identifiers (pid and form_pid parameters) without validating billing ACL permissions or binding the action to the authenticated user's authorized patient context. An authenticated core user can bypass billing authorization checks by tampering with POST parameters to record payments for arbitrary patients, leading to integrity corruption of billing records.
Affected products
- OpenEMR OpenEMR before 8.3.0
Timeline
- 2026-08-18: disclosed
- 2026-11-08: advisory