CVE-2024-50623
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.
do firstApply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. Unrestricted file upload: a WAF can filter file names and extensions, but it cannot judge what the uploaded file will do.
Also consider: MIME sniff · sandbox storage
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2024-50623 being exploited?
Yes. CVE-2024-50623 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-50623?
CVE-2024-50623 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2024-50623?
Yes. A fix has been recorded for CVE-2024-50623. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-50623 affect?
CVE-2024-50623 affects cleo:harmony, cleo:lexicom, cleo:vltrader. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
public exploits
Unvetted proof-of-concept code on GitHub: 4 GitHub proofs of concept · 1 Nuclei template
- Cleo Harmony < 5.8.0.21 - Arbitary File Read · detection template · high
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- total
Assessed by CISA 31 Jul 2026 (SSVC 2.0.3).
timeline
- 28 Oct 2024Published
- 11 Dec 2024First proof-of-concept repository on GitHub (unvetted) · 44 days later
- 13 Dec 2024Added to CISA KEV (exploited in the wild) · 2 days later
- 3 Jan 2025CISA remediation due date (US federal agencies) · 21 days later
- 31 Jul 2026CISA SSVC assessment: exploitation active · 574 days (about 2 years) later
- 7 Oct 2026CVE record last updated · 69 days (about 2 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 26 days later
- Linksupport.cleo.com /hc/en-us/articles/27140294267799-Cleo-Product-Security-Advisory
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-50623
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Nuclei templates: detection templates
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.