dbcve.org
Moveit TransferApplication · Progress

CVE-2023-35708

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-16
Fix available
A fix is available. Upgrade to 2020.1.10 / 2021.0.8 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click Patch available

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.8 (13.0.8), 2021.1.6 (13.1.6), 2022.0.6 (14.0.6), 2022.1.7 (14.1.7), and 2023.0.3 (15.0.3), a SQL injection vulnerability has been identified in the MOVEit Transfer web application that could allow an unauthenticated attacker to gain unauthorized access to MOVEit Transfer's database. An attacker could submit a crafted payload to a MOVEit Transfer application endpoint that could result in modification and disclosure of MOVEit database content. These are fixed versions of the DLL drop-in: 2020.1.10 (12.1.10), 2021.0.8 (13.0.8), 2021.1.6 (13.1.6), 2022.0.6 (14.0.6), 2022.1.7 (14.1.7), and 2023.0.3 (15.0.3).

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
How this class of weakness works · CWE-89

User input is woven into a database query, letting an attacker rewrite the query's logic. From there they can read, alter, or destroy data — frequently the entire database. The reliable fix is parameterised queries (prepared statements), so input is always treated as data and never as SQL.

General guidance for the sql injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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 TransferApplication
Affected:< 2020.1.10>= 2021.0.6, < 2021.0.8>= 2021.1.4, < 2021.1.6>= 2022.0.4, < 2022.0.6>= 2022.1.5, < 2022.1.7>= 2023.0.1, < 2023.0.3

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

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 2020.1.10 / 2021.0.8 / 2021.1.6 or later
Fixed in 2020.1.102021.0.82021.1.6
Vendor patch community.progress.com →
Recommended fix High confidence

Upgrade to the minimum fixed version for your branch: 2020.1.10, 2021.0.8, 2021.1.6, 2022.0.6, 2022.1.7, or 2023.0.3

  1. 1. Identify the current installed version of MOVEit Transfer by checking the application or DLL version information
  2. 2. Determine which upgrade path applies based on current version (2020.1.x -> 2020.1.10, 2021.0.x -> 2021.0.8, 2021.1.x -> 2021.1.6, 2022.0.x -> 2022.0.6, 2022.1.x -> 2022.1.7, or 2023.0.x -> 2023.0.3)
  3. 3. Download the appropriate fixed DLL drop-in or full installer from the official Progress website at https://www.progress.com/products/moveit
  4. 4. Review the official patch release notes at https://community.progress.com/s/article/MOVEit-Transfer-Critical-Vulnerability-15June2023 for any specific installation prerequisites
  5. 5. Backup the current MOVEit Transfer installation and database before applying the upgrade
  6. 6. Apply the patch/upgrade following the vendor's documented upgrade procedure
  7. 7. Verify the fix was applied successfully by confirming the new version number and testing critical functionality
Caveat Review release notes for any compatibility considerations; patches are generally designed as drop-in upgrades but verify database compatibility

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35708 — 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-35708 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