# CVE-2018-15139: File upload in n/a

> Authenticated attackers can upload malicious PHP files to execute arbitrary code on OpenEMR installations.

- **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:** 13 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r3wf-qw98-rgj3

## What is CVE-2018-15139?

CVE-2018-15139 is a high-severity vulnerability in Open-Emr Openemr, published on 13 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unrestricted file upload in interface/super/manage_site_files.php in versions of OpenEMR before 5.0.1.4 allows a remote authenticated attacker to execute arbitrary PHP code by uploading a file with a PHP extension via the images upload form and accessing it in the images directory.

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

## Which versions are affected by CVE-2018-15139?

It affects 1 product.


Products: Open-Emr Openemr.

## How do I fix CVE-2018-15139?

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

## Is CVE-2018-15139 being exploited?

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

Public exploit code:

- OpenEMR < 5.0.1.4 - (Authenticated) File upload - Remote command execution (github_poc): https://github.com/sec-it/exploit-CVE-2018-15139
- OpenEMR 5.0.1.3 - 'manage_site_files' Remote Code Execution (Authenticated) (exploitdb)
- OpenEMR 5.0.1.3 - 'manage_site_files' Remote Code Execution (Authenticated) (2) (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-2018-15139 and fix it if it is affected.

What it is: CVE-2018-15139 is a high-severity vulnerability in Open-Emr Openemr, published on 13 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15139 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-2018-15139/ (Markdown: https://insights.sbomify.com/CVE-2018-15139/index.md)
```

## Sources

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

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