CVE-2025-11235
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 · uneditedUnverified Password Change vulnerability in Progress MOVEit Transfer on Windows (REST API modules).This issue affects MOVEit Transfer: from 2023.1.0 before 2023.1.3, from 2023.0.0 before 2023.0.8, from 2022.1.0 before 2022.1.11, from 2022.0.0 before 2022.0.10.
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 confidenceAn unverified password change vulnerability exists in the MOVEit Transfer REST API on Windows. The flaw allows an authenticated or possibly unauthenticated attacker to modify user passwords without proper verification, potentially gaining unauthorized access to user accounts and sensitive file transfer data.
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>= 2022.0.0, < 2022.0.10>= 2022.1.0, < 2022.1.11>= 2023.0.0, < 2023.0.8>= 2023.1.0, < 2023.1.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed MOVEit Transfer versionCheck the version of MOVEit Transfer installed on the Windows server. This is typically visible in the application admin interface, in the Windows Programs and Features list, or in the installation directory. Compare the version number against the affected ranges: 2022.0.0 through 2022.0.9, 2022.1.0 through 2022.1.10, 2023.0.0 through 2023.0.7, or 2023.1.0 through 2023.1.2.Affected if The installed version falls within any of the affected version ranges listed.
-
Confirm REST API is accessibleVerify that the MOVEit Transfer REST API endpoint is exposed and accessible on the Windows host. The vulnerability exists specifically in the REST API component. Check if API endpoints are reachable via network or if the web interface is available.Affected if The REST API is enabled and accessible on the server.
-
Review user account audit logs for unauthorized password modificationsExamine MOVEit Transfer user activity and audit logs for any password change events that were not initiated by legitimate administrators or users. Look for password change operations, especially those occurring at unusual times, from unexpected sources, or affecting privileged accounts.Affected if Password change records exist in logs that were not initiated by authorized users or that show unexpected modification patterns.
-
Check for unexpected new user accountsReview the list of user accounts in MOVEit Transfer for any accounts that were created without authorization, particularly accounts with elevated privileges or access to sensitive transfer folders.Affected if User accounts exist that were not created through legitimate administrative processes.
A user is affected if MOVEit Transfer is running a version within the affected ranges AND the REST API is accessible, or if audit logs show unauthorized password change activity.
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.102022.1.112023.0.8
Upgrade MOVEit Transfer to the patched versions: 2023.1.3, 2023.0.8, 2022.1.11, or 2022.0.10 or later. Review user account activity logs for unauthorized password changes.
MOVEit Transfer 2022.0.10, 2022.1.11, 2023.0.8, or 2023.1.3 (minimum fixed version based on your current branch)
- Identify the currently installed MOVEit Transfer version from the administration interface or system information
- Download the appropriate fixed version from Progress's official download portal (mysupport.progress.com) or authorized distribution channels
- Review the MOVEit Transfer upgrade guide available at docs.progress.com for your specific version path
- Create a complete backup of the MOVEit Transfer database and configuration files
- Schedule a maintenance window as upgrades may require service interruption
- Stop the MOVEit Transfer services before beginning the upgrade
- Run the installer for the target fixed version (2022.0.10, 2022.1.11, 2023.0.8, or 2023.1.3 depending on your upgrade path)
- Follow post-installation verification steps in the upgrade documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11235 — 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-2025-11235 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