CVE-2023-40043
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 · uneditedIn 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 web interface that could allow a MOVEit system administrator account to gain unauthorized access to the MOVEit Transfer database. A MOVEit system administrator could submit a crafted payload to the MOVEit Transfer web 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 confidenceA SQL injection vulnerability exists in the MOVEit Transfer web interface in versions prior to 2021.1.8, 2022.0.8, 2022.1.9, and 2023.0.6. An authenticated MOVEit system administrator can submit a crafted SQL payload through the web interface to gain unauthorized access to the database, potentially modifying or disclosing database content.
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< 2021.1.8>= 2022.0.0, < 2022.0.8>= 2022.1.0, < 2022.1.9>= 2023.0.0, < 2023.0.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm MOVEit Transfer is installedCheck the installed product by reviewing the Moveit Transfer installation directory, typically found under C:\Program Files\Progress\Moveit Transfer\ or /opt/moveit/transfer/. Look for the MOVEit Transfer application files and components.Affected if MOVEit Transfer software is present on the system
-
Identify installed versionLocate the version information in the installation directory. The version can often be found in an about page, readme, or configuration file within the MOVEit Transfer installation folder. Alternatively, access the MOVEit Transfer web interface and check the help or about section.Affected if The installed version is lower than 2021.1.8, or falls between 2022.0.0-2022.0.7, 2022.1.0-2022.1.8, or 2023.0.0-2023.0.5
-
Verify web interface is accessibleAttempt to access the MOVEit Transfer web portal via HTTP/HTTPS at the configured hostname or IP address. Confirm the login page is reachable.Affected if The web interface is exposed and reachable from a network where an attacker could obtain administrator credentials
-
Confirm system administrator accounts existReview the MOVEit Transfer user management console or database user tables to identify if any system administrator accounts are configured. Check for the presence of admin-level accounts in the user repository.Affected if There are active system administrator accounts configured in MOVEit Transfer, providing a potential attack vector for the SQL injection
A user is affected if MOVEit Transfer is installed with a version prior to 2021.1.8, 2022.0.8, 2022.1.9, or 2023.0.6, and the web interface with administrator accounts is accessible.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2021.1.82022.0.82022.1.9
Apply the vendor-supplied patches to upgrade MOVEit Transfer to version 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. Verify database integrity after patching.
Upgrade to the appropriate fixed version: 2021.1.8, 2022.0.8, 2022.1.9, or 2023.0.6 depending on your current version branch
- 1. Identify the current installed version of MOVEit Transfer by checking the application or system information
- 2. Determine which version branch your current installation is on (2021.x, 2022.0.x, 2022.1.x, or 2023.x)
- 3. If on 2021.x branch: Upgrade to version 2021.1.8 (13.1.8) or later
- 4. If on 2022.0.x branch: Upgrade to version 2022.0.8 (14.0.8) or later
- 5. If on 2022.1.x branch: Upgrade to version 2022.1.9 (14.1.9) or later
- 6. If on 2023.x branch: Upgrade to version 2023.0.6 (15.0.6) or later
- 7. After upgrading, verify the MOVEit Transfer web interface is functioning correctly
- 8. Confirm the SQL injection vulnerability is remediated by verifying the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40043 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-40043 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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