dbcve.org
Moveit TransferApplication · Progress

CVE-2023-35036

CRITICAL · 9.1 CVSS v3.1 Published 2023-06-12
Fix available
A fix is available. Upgrade to 2021.0.7 / 2021.1.5 or later.
See remediation →
100/100
Remediation priority · Urgent
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.7 (13.0.7), 2021.1.5 (13.1.5), 2022.0.5 (14.0.5), 2022.1.6 (14.1.6), and 2023.0.2 (15.0.2), SQL injection vulnerabilities have been found 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.

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

Unauthenticated SQL injection vulnerability in MOVEit Transfer web application endpoints allows attackers to submit crafted payloads that can modify and disclose MOVEit database content, achieving unauthorized database access without credentials.

MitigationApply the vendor-supplied patches for all affected versions (2021.0.7, 2021.1.5, 2022.0.5, 2022.1.6, 2023.0.2 and later) to remediate the SQL injection vectors.

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.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
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm MOVEit Transfer installation
    Locate the MOVEit Transfer application on the server. On Windows, check Programs and Features or the installation directory (commonly C:\Program Files\Progress\MOVEit Transfer or C:\MOVEitTransfer). On Linux, check /opt/MOVEit or the installation path used during setup.
    Affected if MOVEit Transfer is installed and the version falls within the affected ranges
  2. Identify installed version
    Locate the version information. In the web interface, log in as an administrator and navigate to Help > About or the system information page. Alternatively, check the installer log files or the dll/version file in the installation directory. The version typically displays as x.y.z (e.g., 2022.1.5).
    Affected if The installed version is less than 2021.0.7, or is 2021.1.0-2021.1.4, 2022.0.0-2022.0.4, 2022.1.0-2022.1.5, or 2023.0.0-2023.0.1
  3. Determine web interface exposure
    Identify if the MOVEit Transfer web application (typically on IIS) is accessible from external networks or the internet. Check IIS Manager for the MOVEit site bindings and review firewall or network ACL rules that permit access to ports 80/443 (or custom ports).
    Affected if The web interface is exposed to untrusted networks and the installed version is vulnerable
  4. Review web server logs for suspicious SQL-like patterns
    Examine the IIS or web server access logs for MOVEit Transfer. Search for SQL injection indicators such as single quotes ('), UNION SELECT, OR 1=1, or other SQL keywords in URL parameters, especially on unauthenticated endpoints. Logs are typically in C:\inetpub\logs\LogFiles or the configured log directory.
    Affected if Unusual SQL syntax patterns appear in the web logs targeting MOVEit endpoints
  5. Check for unauthorized database access indicators
    Review database audit logs or MOVEit transaction logs for unusual queries, especially those executed without valid authentication sessions or outside normal application behavior patterns. Check for unexpected data exports or modifications.
    Affected if Database queries appear that were not initiated by legitimate authenticated users or admin actions

If MOVEit Transfer version is below 2021.0.7, between 2021.1.0-2021.1.4, between 2022.0.0-2022.0.4, between 2022.1.0-2022.1.5, or between 2023.0.0-2023.0.1 and the web interface is accessible, the environment is likely affected by this unauthenticated SQL injection vulnerability.

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.0.7 / 2021.1.5 / 2022.0.5 or later
Fixed in 2021.0.72021.1.52022.0.5
Interim mitigation

Apply the vendor-supplied patches for all affected versions (2021.0.7, 2021.1.5, 2022.0.5, 2022.1.6, 2023.0.2 and later) to remediate the SQL injection vectors.

Recommended fix High confidence

Upgrade to 2023.0.2 (15.0.2) for latest branch, or 2022.1.6 (14.1.6), 2022.0.5 (14.0.5), or 2021.1.5 (13.1.5) depending on current version branch

  1. Identify the current Moveit Transfer version by checking the application or system information
  2. Determine the appropriate upgrade path based on current version: if using 2021.0.x upgrade to 2021.0.7; if using 2021.1.x upgrade to 2021.1.5; if using 2022.0.x upgrade to 2022.0.5; if using 2022.1.x upgrade to 2022.1.6; if using 2023.0.x or earlier upgrade to 2023.0.2
  3. Obtain the fixed version from the official Progress Software download portal or support site
  4. Review the MOVEit Transfer upgrade documentation before proceeding
  5. Execute the upgrade following vendor-provided upgrade procedures
  6. After upgrade, verify the application is running the patched version
  7. Confirm the SQL injection vulnerability is remediated by testing or reviewing release notes
Caveat Review release notes for any configuration or compatibility changes; test upgrade in staging environment 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
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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