CVE-2026-5174
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 · uneditedImproper input validation vulnerability in Progress Software MOVEit Automation allows Privilege Escalation. This issue affects MOVEit Automation: from 2025.1.0 before 2025.1.5, from 2025.0.0 before 2025.0.9, from 2024.0.0 before 2024.1.8, versions prior to 2024.0.0.
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 confidenceImproper input validation in Progress Software MOVEit Automation allows authenticated users to escalate privileges to higher permission levels, potentially gaining administrative access to the application.
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< 2024.1.8>= 2025.0.0, < 2025.1.5CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate the installed MOVEit Automation versionAccess the MOVEit Automation admin interface, typically via Settings > System > About, or check the installation directory for version metadataAffected if The version displayed is less than 2024.1.8, or is 2025.0.0 through 2025.1.4 inclusive
-
Confirm user authentication is enabledVerify that MOVEit Automation user accounts exist and the application accepts authenticated loginsAffected if The application has active user accounts configured for authentication (the vulnerability requires an authenticated session to exploit)
-
Check for recent privilege escalation indicatorsReview MOVEit Automation audit logs or user permission assignments for unexpected changes to user roles or administrative accessAffected if Any user account shows elevated permissions that were not explicitly assigned through standard administration
A MOVEit Automation installation is affected if it runs version 2024.1.7 or earlier, or any version from 2025.0.0 through 2025.1.4, and has authenticated user accounts configured.
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 · scoped2024.1.82025.1.5
Apply the vendor patches by upgrading MOVEit Automation to version 2025.1.5, 2025.0.9, or 2024.1.8 or later to remediate the input validation flaw.
MOVEit Automation 2025.1.5 (or latest available version)
- 1. Back up the MOVEit Automation database and configuration files
- 2. Download MOVEit Automation version 2025.1.5 (or latest available version) from the Progress Software customer portal at community.progress.com
- 3. Review the upgrade guide provided by Progress Software for MOVEit Automation
- 4. Stop all MOVEit Automation services
- 5. Install the upgrade following the documented upgrade procedure
- 6. Verify the installation completed successfully
- 7. Restart MOVEit Automation services
- 8. Confirm the vulnerability is resolved by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $5,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5174 — 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-2026-5174 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