dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Jun 2023. Known ransomware use
Moveit CloudApplication · Progress

CVE-2023-34362

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-02
Fix available
A fix is available. Upgrade to 14.0.5.45 / 14.1.6.97 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL injection vulnerability in Progress MOVEit Transfer web application allows unauthenticated attackers to execute arbitrary SQL statements against the database, potentially exposing or modifying sensitive data. The vulnerability affects multiple database engines (MySQL, Microsoft SQL Server, Azure SQL) and was actively exploited in the wild.

MitigationApply the vendor-supplied patches to move to version 2021.0.6, 2021.1.4, 2022.0.4, 2022.1.5, or 2023.0.1 or later to remediate this critical vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Moveit CloudApplication
Affected:< 14.0.5.45>= 14.1.0.0, < 14.1.6.97>= 15.0.0.0, < 15.0.2.39
Moveit TransferApplication
Affected:< 2021.0.7>= 2021.1.0, < 2021.1.5>= 2022.0.0, < 2022.0.5>= 2022.1.0, < 2022.1.6>= 2023.0.0, < 2023.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify MOVEit Transfer installation and version
    Locate the MOVEit Transfer installation directory and check the version file, typically in the installation root folder. The version is often stored in a version.txt, about screen in the web UI, or can be retrieved via the /api/v1/Version endpoint if accessible.
    Affected if The installed version falls within any of these ranges: < 2021.0.7; >= 2021.1.0 and < 2021.1.5; >= 2022.0.0 and < 2022.0.5; >= 2022.1.0 and < 2022.1.6; >= 2023.0.0 and < 2023.0.2 for MOVEit Transfer. For MOVEit Cloud: < 14.0.5.45; >= 14.1.0.0 and < 14.1.6.97; >= 15.0.0.0 and < 15.0.2.39.
  2. Verify web application accessibility
    Determine if the MOVEit Transfer web interface (ports 80/443 or configured HTTP/HTTPS ports) is accessible from untrusted networks such as the internet orDMZ. Check firewall rules, reverse proxy configurations, and network ACLs.
    Affected if The MOVEit Transfer web application is directly exposed to the internet or accessible from untrusted networks without proper network segmentation or authentication gating.
  3. Review web server access logs for SQL injection indicators
    Examine IIS or other web server logs in the MOVEit Transfer log directory for suspicious GET or POST requests targeting endpoints, especially those containing SQL keywords (SELECT, UNION, INSERT, DROP) in query parameters or unusual patterns in the /api/ route.
    Affected if Log entries show requests with SQL injection patterns, especially to /api/v1/ folder endpoints, or repeated requests with unusual parameter manipulation that could indicate exploitation attempts.
  4. Check for unauthorized database access indicators
    Review database audit logs, user creation events, or unexpected data exports. Examine database tables for new administrative accounts, modified permissions, or suspicious stored procedures created after the vulnerability disclosure date (June 2023).
    Affected if Database shows evidence of unauthorized queries, new accounts, or data access that was not initiated by legitimate administrators, particularly if timestamps align with June 2023 or later.

You are affected if MOVEit Transfer or MOVEit Cloud is running a version within the affected ranges AND the web interface is network-accessible, regardless of whether signs of exploitation are yet observed in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.0.5.45 / 14.1.6.97 / 15.0.2.39 or later
Fixed in 14.0.5.4514.1.6.9715.0.2.39
Interim mitigation

Apply the vendor-supplied patches to move to version 2021.0.6, 2021.1.4, 2022.0.4, 2022.1.5, or 2023.0.1 or later to remediate this critical vulnerability.

Recommended fix High confidence

Moveit Transfer: upgrade to 2021.0.7, 2021.1.5, 2022.0.5, 2022.1.6 or later; Moveit Cloud: upgrade to 14.0.5.45, 14.1.6.97, 15.0.2.39 or later

  1. Identify the currently installed MOVEit Transfer or MOVEit Cloud version by checking the application's 'Help > About' or the administrative interface
  2. For MOVEit Cloud customers: Contact Progress Software support to request the upgrade to version 14.0.5.45, 14.1.6.97, or 15.0.2.39 or later
  3. For MOVEit Transfer customers: Upgrade to one of the fixed versions: 2021.0.7, 2021.1.5, 2022.0.5, 2022.1.6, or later
  4. Download the appropriate installer from the official Progress Software download portal (community.progress.com) or via the customer support channel
  5. Schedule a maintenance window and follow Progress Software's standard upgrade procedure for MOVEit Transfer
  6. After upgrade, verify the application version reflects the patched release
  7. Review database access logs for any suspicious activity dating back to May 2023, as exploitation occurred in the wild
  8. Ensure web application firewall (WAF) rules are in place as an additional layer of defense
Caveat Standard upgrade risks apply - test in non-production environment first, backup database, verify compatibility with integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Moveit Cloud Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-34362 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-34362 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data