# CVE-2017-9380: File upload in n/a

> Low-privilege users can upload malicious files to OpenEMR, leading to arbitrary code execution on the server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-493f-ffrh-hqvq

## What is CVE-2017-9380?

CVE-2017-9380 is a high-severity vulnerability in Open-Emr Openemr, published on 2 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenEMR 5.0.0 and prior allows low-privilege users to upload files of dangerous types which can result in arbitrary code execution within the context of the vulnerable application.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2017-9380?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2017-9380?

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

## Is CVE-2017-9380 being exploited?

There is no known exploitation of CVE-2017-9380 in the wild and no public exploit code.

Public exploit code:

- OpenEMR 5.0.0 - Remote Code Execution (Authenticated) (exploitdb)

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9380 and fix it if it is affected.

What it is: CVE-2017-9380 is a high-severity vulnerability in Open-Emr Openemr, published on 2 Jun 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9380 in the wild and no public exploit code.

Affected product: Open-Emr 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-2017-9380/ (Markdown: https://insights.sbomify.com/CVE-2017-9380/index.md)
```

## Sources

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

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