CVE-2023-6217
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 2022.0.9 (14.0.9), 2022.1.10 (14.1.10), 2023.0.7 (15.0.7), a reflected cross-site scripting (XSS) vulnerability has been identified when MOVEit Gateway is used in conjunction with MOVEit Transfer. An attacker could craft a malicious payload targeting the system which comprises a MOVEit Gateway and MOVEit Transfer deployment. If a MOVEit user interacts with the crafted payload, the attacker would be able to execute malicious JavaScript within the context of the victim’s browser.
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 confidenceThis is a reflected cross-site scripting (XSS) vulnerability in Progress MOVEit Transfer that occurs specifically when MOVEit Gateway is deployed in conjunction with MOVEit Transfer. An attacker can craft a malicious URL containing JavaScript payload that, when clicked by a MOVEit user, executes in the victim's browser session.
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.0>= 2022.0.0, < 2022.0.9>= 2022.1.0, < 2022.1.10>= 2023.0.0, < 2023.0.7>= 2023.1.0, < 2023.1.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify MOVEit Transfer installation and versionLog into the MOVEit Transfer admin interface and navigate to Help > About, or check the installation directory for version information in the application files or logsAffected if The installed version falls within any of these ranges: <=2021.1.0, >=2022.0.0 and <2022.0.9, >=2022.1.0 and <2022.1.10, >=2023.0.0 and <2023.0.7, or >=2023.1.0 and <2023.1.2
-
Determine if MOVEit Gateway is deployedCheck the MOVEit Transfer admin interface under System > Gateway or examine the server configuration for MOVEit Gateway components. Alternatively, review the installed services and web applications on the server for MOVEit Gateway modulesAffected if MOVEit Gateway is installed and integrated with MOVEit Transfer, as this combination is required for the XSS vulnerability to be exploitable
-
Inspect HTTP traffic for suspicious URL patternsReview web server access logs or proxy logs for incoming requests to MOVEit Transfer that contain script tags or JavaScript code in URL parameters, particularly in paths typically associated with MOVEit Gateway endpointsAffected if Unexpected or malicious URL patterns containing XSS payloads are found in the logs targeting the MOVEit environment
The environment is affected if MOVEit Transfer version is within the vulnerable ranges listed AND MOVEit Gateway is deployed alongside it, enabling the reflected XSS attack vector.
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 · scoped2022.0.92022.1.102023.0.7
Upgrade MOVEit Transfer to version 2022.0.9 (14.0.9), 2022.1.10 (14.1.10), or 2023.0.7 (15.0.7) or later per the fixed version corresponding to the deployed branch.
Upgrade to MOVEit Transfer 2022.0.9 (14.0.9), 2022.1.10 (14.1.10), or 2023.0.7 (15.0.7) depending on your current version branch
- 1. Identify the current MOVEit Transfer version installed in your environment
- 2. Based on your current version line, determine the appropriate upgrade target: if <=2021.1.0, upgrade to 2022.0.9 or later; if >=2022.0.0 and <2022.0.9, upgrade to 2022.0.9; if >=2022.1.0 and <2022.1.10, upgrade to 2022.1.10; if >=2023.0.0 and <2023.0.7, upgrade to 2023.0.7
- 3. Review the MOVEit Transfer upgrade guide and release notes from Progress for the target version
- 4. Perform a backup of the current MOVEit Transfer configuration and database
- 5. Execute the upgrade following Progress documentation procedures
- 6. Verify the installation by checking the MOVEit Transfer version number in the admin interface
- 7. Confirm the XSS vulnerability is remediated by verifying the MOVEit Gateway integration works correctly
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-6217 — 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-6217 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