CVE-2023-6218
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 privilege escalation path associated with group administrators has been identified. It is possible for a group administrator to elevate a group members permissions to the role of an organization administrator.
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 privilege escalation vulnerability in Progress MOVEit Transfer file transfer software. A group administrator can elevate a group member's permissions to the role of organization administrator, bypassing the intended permission boundaries between group and organization administrative roles.
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
- 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.
-
Verify MOVEit Transfer is installedCheck for the MOVEit Transfer web application in IIS Manager or look for the installation directory (typically C:\Program Files\MOVEit Transfer or /opt/MOVEit/Transfer)Affected if MOVEit Transfer software is present on the system
-
Determine installed versionAccess the MOVEit Transfer web interface and check the version displayed in the help/about section, or inspect the assembly version in the installed binariesAffected 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; >= 2023.1.0 and < 2023.1.2
-
Confirm group administrative roles existLog into the MOVEit Transfer admin interface and navigate to the user/group management section. Look for users assigned the 'Group Administrator' roleAffected if At least one user is assigned the Group Administrator role in MOVEit Transfer
-
Check for organization administrator rolesIn the admin interface, verify if Organization Administrator roles are configured and review the membership of administrative groupsAffected if Both Group Administrator and Organization Administrator roles are present in the environment
-
Audit recent permission changesReview MOVEit Transfer audit logs or security logs for any recent changes where group members were promoted to organization-level permissionsAffected if Any suspicious elevation of group members to organization administrator permissions are found in logs
You are affected if MOVEit Transfer is installed and the version is within the vulnerable ranges listed AND your environment has group administrator accounts that could potentially be exploited for privilege escalation.
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), 2023.0.7 (15.0.7) or later. Review existing group administrator assignments and audit permission changes for any signs of exploitation.
2022.0.9, 2022.1.10, or 2023.0.7 (or later respective releases)
- Identify your current MOVEit Transfer version from the administration interface or system information
- Determine which version branch you are currently running (2021.x, 2022.0.x, 2022.1.x, or 2023.0.x)
- Upgrade to a fixed release: For 2021.x users, upgrade to 2022.0.9 or later (or 2022.1.10 or later, or 2023.0.7 or later)
- For 2022.0.x users, upgrade to version 2022.0.9 or later
- For 2022.1.x users, upgrade to version 2022.1.10 or later
- For 2023.0.x users, upgrade to version 2023.0.7 or later
- After upgrade, verify the group administrator privilege escalation vulnerability is resolved by testing that group administrators can no longer elevate member permissions to organization administrator
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6218 — 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-6218 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