# CVE-2024-50623: Cleo Multiple Products Unrestricted File Upload

> Attackers can upload malicious files to Cleo Harmony, VLTrader, or LexiCom servers to achieve remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 13 Dec 2024 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2024
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-8j74-v9cr-x39h

## What is CVE-2024-50623?

CVE-2024-50623 is a critical vulnerability in n/a, published on 27 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Cleo Harmony before 5.8.0.21, VLTrader before 5.8.0.21, and LexiCom before 5.8.0.21, there is an unrestricted file upload and download that could lead to remote code execution.

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

## Which versions are affected by CVE-2024-50623?

It affects 3 products.


Products: Cleo Harmony, Cleo Lexicom, Cleo Vltrader.

## How do I fix CVE-2024-50623?

No fix has been published for CVE-2024-50623 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 Jan 2025.

## Is CVE-2024-50623 being exploited?

Yes. Attackers have exploited CVE-2024-50623 in the wild since at least 13 Dec 2024, including in ransomware campaigns.

Public exploit code:

- Cleo Unrestricted file upload and download PoC (CVE-2024-50623) (github_poc): https://github.com/watchtowrlabs/CVE-2024-50623
- CVE-2024-50623 POC - Cleo Unrestricted file upload and download (github_poc): https://github.com/verylazytech/CVE-2024-50623
- Cleo 远程代码执行漏洞批量检测脚本（CVE-2024-50623） (github_poc): https://github.com/iSee857/Cleo-CVE-2024-50623-PoC
- https://github.com/congdong007/CVE-2024-50623-poc (github_poc): https://github.com/congdong007/CVE-2024-50623-poc
- Cleo Harmony < 5.8.0.21 - Arbitary File Read (nuclei): http/cves/2024/CVE-2024-50623.yaml

## Other vulnerabilities in n/a

- [CVE-2024-55956](https://insights.sbomify.com/CVE-2024-55956/): Cleo Multiple Products Unauthenticated File Upload (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50623 and fix it if it is affected.

What it is: CVE-2024-50623 is a critical vulnerability in n/a, published on 27 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2024-50623 in the wild since at least 13 Dec 2024, including in ransomware campaigns.

Affected product: n/a. 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-2024-50623/ (Markdown: https://insights.sbomify.com/CVE-2024-50623/index.md)
```

## Sources

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

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