# CVE-2023-34362: Progress MOVEit Transfer SQL Injection

> Unauthenticated attackers can exploit SQL injection to read, alter, or delete database contents in MOVEit Transfer.

- **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 2 Jun 2023 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-hq22-q5g8-577g

## What is CVE-2023-34362?

CVE-2023-34362 is a critical SQL injection vulnerability in n/a, published on 2 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Progress MOVEit Transfer before 2021.0.6 (13.0.6), 2021.1.4 (13.1.4), 2022.0.4 (14.0.4), 2022.1.5 (14.1.5), and 2023.0.1 (15.0.1), a SQL injection vulnerability has been found in the MOVEit Transfer web application that could allow an unauthenticated attacker to gain access to MOVEit Transfer's database. Depending on the database engine being used (MySQL, Microsoft SQL Server, or Azure SQL), an attacker may be able to infer information about the structure and contents of the database, and execute SQL statements that alter or delete database elements. NOTE: this is exploited in the wild in May and June 2023; exploitation of unpatched systems can occur via HTTP or HTTPS. All versions (e.g., 2020.0 and 2019x) before the five explicitly mentioned versions are affected, including older unsupported versions.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-34362?

It affects 2 products.


Products: Progress Moveit Cloud, Progress Moveit Transfer.

## How do I fix CVE-2023-34362?

No fix has been published for CVE-2023-34362 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 23 Jun 2023.

## Is CVE-2023-34362 being exploited?

Yes. Attackers have exploited CVE-2023-34362 in the wild since at least 2 Jun 2023, including in ransomware campaigns.

Public exploit code:

- MOVEit CVE-2023-34362 (github_poc): https://github.com/horizon3ai/CVE-2023-34362
- CVE-2023-34362: MOVEit Transfer Unauthenticated RCE (github_poc): https://github.com/sfewer-r7/CVE-2023-34362
- POC for CVE-2023-34362 affecting MOVEit Transfer (github_poc): https://github.com/Malwareman007/CVE-2023-34362
- Repository with everything I have tracking the impact of MOVEit CVE-2023-34362 (github_poc): https://github.com/kenbuckler/MOVEit-CVE-2023-34362
- CVE-2023-34362-IOCs. More information on Deep Instinct's blog site. (github_poc): https://github.com/deepinstinct/MOVEit_CVE-2023-34362_IOCs
- an exploit of POC for CVE-2023-34362 affecting MOVEit Transfer (github_poc): https://github.com/errorfiathck/MOVEit-Exploit

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34362 and fix it if it is affected.

What it is: CVE-2023-34362 is a critical SQL injection vulnerability in n/a, published on 2 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-34362 in the wild since at least 2 Jun 2023, 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-2023-34362/ (Markdown: https://insights.sbomify.com/CVE-2023-34362/index.md)
```

## Sources

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

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