# CVE-2026-124450: OpenEMR before 8.3.0 Arbitrary File Read/Write via disposeDocument


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:H/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-cq78-6jw9-4cxm, GHSA-wf4w-mx2w-j4vv

## What is CVE-2026-124450?

CVE-2026-124450 is a critical vulnerability in openemr, published on 8 Nov 2026. 

### Official description

OpenEMR before 8.3.0 contains a broken access control and path traversal vulnerability in the fax/sms module disposeDocument action via an unvalidated file_path parameter. Authenticated low-privilege users can read sqlconf.php to recover database credentials and write arbitrary files as the web user, enabling remote code execution.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

No fix has been published for CVE-2026-124450 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124450 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124450 exists.

Public exploit code:

- OpenEMR before 8.3.0 Arbitrary File Read/Write via disposeDocument (github_poc): https://github.com/Nxploited/CVE-2026-124450

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124450 and fix it if it is affected.

What it is: CVE-2026-124450 is a critical vulnerability in openemr, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124450 exists.

Affected product: openemr. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124450/ (Markdown: https://insights.sbomify.com/CVE-2026-124450/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124450
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124450
- OSV: https://osv.dev/vulnerability/CVE-2026-124450

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124450/
Summaries are generated and may contain mistakes; the official description above is the record.