# CVE-2020-37009: MedDream PACS Server 6.8.3.751 - Remote Code Execution

> Authenticated attackers can upload malicious PHP files to MedDream PACS Server to execute arbitrary system commands with elevated privileges.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 29 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-hxfj-rc88-5v2p

## What is CVE-2020-37009?

CVE-2020-37009 is a high-severity vulnerability in MedDream PACS Server, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MedDream PACS Server 6.8.3.751 contains an authenticated remote code execution vulnerability that allows authorized users to upload malicious PHP files. Attackers can exploit the uploadImage.php endpoint by authenticating and uploading a PHP shell to execute arbitrary system commands with elevated privileges.

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

## Which versions are affected by CVE-2020-37009?


## How do I fix CVE-2020-37009?

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

## Is CVE-2020-37009 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37009 and fix it if it is affected.

What it is: CVE-2020-37009 is a high-severity vulnerability in MedDream PACS Server, published on 29 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-37009 exists.

Affected product: MedDream PACS Server. 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-2020-37009/ (Markdown: https://insights.sbomify.com/CVE-2020-37009/index.md)
```

## Sources

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

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