dbcve.org
Moveit TransferApplication · Progress

CVE-2023-42660

HIGH · 8.8 CVSS v3.1 Published 2023-09-20
Fix available
A fix is available. Upgrade to 2021.1.8 / 2022.0.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 versions released before 2021.1.8 (13.1.8), 2022.0.8 (14.0.8), 2022.1.9 (14.1.9), 2023.0.6 (15.0.6), a SQL injection vulnerability has been identified in the MOVEit Transfer machine interface that could allow an authenticated attacker to gain unauthorized access to the MOVEit Transfer database. An attacker could submit a crafted payload to the MOVEit Transfer machine interface which could result in modification and disclosure of MOVEit database content.

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

SQL injection vulnerability in MOVEit Transfer's machine interface allows authenticated attackers to submit crafted payloads that can result in unauthorized access, modification, and disclosure of MOVEit database content.

MitigationUpgrade MOVEit Transfer to versions 2021.1.8 (13.1.8), 2022.0.8 (14.0.8), 2022.1.9 (14.1.9), 2023.0.6 (15.0.6) or later to remediate the 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 TransferApplication
Affected:< 2021.1.8>= 2022.0.0, < 2022.0.8>= 2022.1.0, < 2022.1.9>= 2023.0.0, < 2023.0.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Locate the installed MOVEit Transfer version number through the product's about page, help menu, or installation directory. Common locations include the administration console or the program's version information.
    Affected if The installed version falls into any of these ranges: < 2021.1.8, >= 2022.0.0 and < 2022.0.8, >= 2022.1.0 and < 2022.1.9, or >= 2023.0.0 and < 2023.0.6
  2. Verify machine interface is accessible
    Confirm that the MOVEit Transfer machine interface (also known as the MOVEit API or web services endpoint) is exposed and accessible. This is typically available at /MOVEitTransfer/ under the web root.
    Affected if The machine interface endpoint is reachable from the network without being disabled or restricted by network-level controls
  3. Review database access logs
    Inspect MOVEit Transfer's database activity logs, SQL logs, or audit logs for unusual or unauthorized SQL queries, especially those originating from machine interface sessions that the organization did not initiate.
    Affected if Log entries show unexpected SQL statements, elevated privilege queries, or data exfiltration patterns consistent with injection attacks
  4. Check for unauthorized database changes
    Review database tables for unexpected modifications, new user accounts, altered permissions, or data exports that align with the timing of potential exploitation.
    Affected if Database content shows unauthorized modifications, new administrative accounts, or data access that was not initiated by legitimate administrators

A user is affected if their MOVEit Transfer version is within any of the vulnerable version ranges AND the machine interface is accessible to authenticated attackers.

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 2021.1.8 / 2022.0.8 / 2022.1.9 or later
Fixed in 2021.1.82022.0.82022.1.9
Interim mitigation

Upgrade MOVEit Transfer to versions 2021.1.8 (13.1.8), 2022.0.8 (14.0.8), 2022.1.9 (14.1.9), 2023.0.6 (15.0.6) or later to remediate the vulnerability.

Recommended fix High confidence

2021.1.8 (13.1.8), 2022.0.8 (14.0.8), 2022.1.9 (14.1.9), or 2023.0.6 (15.0.6) - choose the relevant version for your branch

  1. 1. Identify the current installed version of MOVEit Transfer by checking the application or system documentation
  2. 2. Determine which version branch you are currently running (2021.x, 2022.0.x, 2022.1.x, or 2023.0.x)
  3. 3. For 2021.x branch: upgrade to version 2021.1.8 (13.1.8) or later
  4. 4. For 2022.0.x branch: upgrade to version 2022.0.8 (14.0.8) or later
  5. 5. For 2022.1.x branch: upgrade to version 2022.1.9 (14.1.9) or later
  6. 6. For 2023.0.x branch: upgrade to version 2023.0.6 (15.0.6) or later
  7. 7. Download the appropriate fixed version from the Progress Customer Portal or official distribution channel
  8. 8. Follow Progress MOVEit Transfer upgrade documentation to apply the update

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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