dbcve.org
Moveit TransferApplication · Progress

CVE-2023-36932

HIGH · 8.1 CVSS v3.1 Published 2023-07-05
Fix available
A fix is available. Upgrade to 2020.1.11 / 2021.0.9 or later.
See remediation →
87/100
Remediation priority · High
High EPSS 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 before 2020.1.11 (12.1.11), 2021.0.9 (13.0.9), 2021.1.7 (13.1.7), 2022.0.7 (14.0.7), 2022.1.8 (14.1.8), and 2023.0.4 (15.0.4), multiple SQL injection vulnerabilities have been identified in the MOVEit Transfer web application that could allow an authenticated attacker to gain unauthorized access to the MOVEit Transfer 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.

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

Multiple SQL injection vulnerabilities in MOVEit Transfer web application allow authenticated attackers to submit crafted payloads to application endpoints, enabling unauthorized access to and modification of the MOVEit database content.

MitigationApply vendor security patches for all affected versions (2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, 2023.0.4) after staged testing in non-production environments and maintain current versions thereafter.

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:< 2020.1.11>= 2021.0, < 2021.0.9>= 2021.1.0, < 2021.1.7>= 2022.0.0, < 2022.0.7>= 2022.1.0, < 2022.1.8>= 2023.0.0, < 2023.0.4

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
None

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

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 MOVEit Transfer installation directory and check the version information. On Windows, this is typically found in the program files or installation folder. Check for a version file, installer log, or the application executable properties that display the current build number.
    Affected if The installed version falls within any of these ranges: < 2020.1.11; >= 2021.0 and < 2021.0.9; >= 2021.1.0 and < 2021.1.7; >= 2022.0.0 and < 2022.0.7; >= 2022.1.0 and < 2022.1.8; >= 2023.0.0 and < 2023.0.4
  2. Confirm MOVEit Transfer web application is running
    Verify the MOVEit Transfer SFTP web service or IIS application pool is active. Check Windows Services for MOVEit services or examine the IIS manager to confirm the MOVEit Transfer web application pool is started and the site is running.
    Affected if The MOVEit Transfer web application is running and accessible, as this is required for the SQL injection to be exploitable
  3. Verify web interface accessibility
    Determine if the MOVEit Transfer web portal is reachable over the network. This can be done by attempting to access the login page from a network perspective or reviewing firewall and network configuration to confirm the application is exposed to potential attackers.
    Affected if The MOVEit Transfer web interface is accessible from network locations where attackers could authenticate and submit crafted payloads
  4. Check for recent security patches
    Review installed updates or patch history on the MOVEit Transfer server. Look for evidence that any of the security updates (2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, or 2023.0.4) have been applied to the installation.
    Affected if No security patches have been installed and the version remains in an affected range

The environment is affected if MOVEit Transfer is running with a version less than the fixed releases (2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, or 2023.0.4) and the web application is accessible to authenticated users.

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 2020.1.11 / 2021.0.9 / 2021.1.7 or later
Fixed in 2020.1.112021.0.92021.1.7
Interim mitigation

Apply vendor security patches for all affected versions (2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, 2023.0.4) after staged testing in non-production environments and maintain current versions thereafter.

Recommended fix High confidence

Upgrade to MOVEit Transfer 2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, or 2023.0.4 (or later) depending on your current version branch

  1. 1. Identify the current MOVEit Transfer version by checking the application or system information
  2. 2. Determine which version branch you are currently running (2020.x, 2021.0.x, 2021.1.x, 2022.0.x, 2022.1.x, or 2023.0.x)
  3. 3. Review the Progress MOVEit Transfer release notes for the applicable fixed version
  4. 4. Plan the upgrade according to Progress official documentation
  5. 5. Create a full backup of the MOVEit Transfer database and configuration
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Schedule a maintenance window for the production upgrade
  8. 8. Apply the upgrade to the fixed version (2020.1.11, 2021.0.9, 2021.1.7, 2022.0.7, 2022.1.8, or 2023.0.4 or later)
Caveat Standard upgrade risks apply - perform regression testing and ensure compatibility with existing integrations before production deployment

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
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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