dbcve.org
Moveit TransferApplication · Progress

CVE-2026-8800

HIGH · 8.8 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2025.0.7 / 2025.1.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 6 weeks old

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 · unedited
Incorrect Authorization vulnerability in Progress MOVEit Transfer (Audit User module). This issue affects MOVEit Transfer: before 2025.0.7, from 2025.1.0 before 2025.1.3.

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 · moderate confidence

Incorrect Authorization vulnerability in the Audit User module of Progress MOVEit Transfer allows users to potentially perform unauthorized actions or access data they shouldn't have permission to access. The vulnerability exists in specific versions before 2025.0.7 and between 2025.1.0 and 2025.1.3.

MitigationUpgrade MOVEit Transfer to version 2025.0.7, 2025.1.3, or later to remediate this authorization vulnerability. Given the HIGH (8.8) CVSS score, prioritize this patch promptly.

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
Moveit TransferApplication
Affected:< 2025.0.7>= 2025.1.1, < 2025.1.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify MOVEit Transfer installed version
    Locate the MOVEit Transfer installation and determine the current version number from the application, installation directory, or admin interface
    Affected if Version is < 2025.0.7 or >= 2025.1.1 but < 2025.1.3
  2. Compare version against vulnerable ranges
    Cross-reference your installed version against the affected ranges: any version before 2025.0.7, or versions 2025.1.1 through 2025.1.2
    Affected if Installed version falls within < 2025.0.7 or >= 2025.1.1 and < 2025.1.3
  3. Verify Audit User module presence
    Confirm the Audit User module is enabled or accessible in your MOVEit Transfer deployment
    Affected if The Audit User module exists and is accessible in the affected version range

Environment is affected if MOVEit Transfer version is before 2025.0.7 or between 2025.1.1-2025.1.3 and the Audit User module is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2025.0.7 / 2025.1.3 or later
Fixed in 2025.0.72025.1.3
Interim mitigation

Upgrade MOVEit Transfer to version 2025.0.7, 2025.1.3, or later to remediate this authorization vulnerability. Given the HIGH (8.8) CVSS score, prioritize this patch promptly.

Recommended fix High confidence

2025.0.7 or later for 2025.0.x line; 2025.1.3 or later for 2025.1.x line

  1. 1. Identify the current installed version of MOVEit Transfer by checking the application or system information
  2. 2. Determine which upgrade path applies: if current version is < 2025.0.7, plan upgrade to 2025.0.7 or later; if current version is >= 2025.1.1 and < 2025.1.3, plan upgrade to 2025.1.3 or later
  3. 3. Review Progress MOVEit Transfer upgrade documentation at docs.progress.com for upgrade prerequisites and procedures
  4. 4. Create a complete backup of the current MOVEit Transfer installation, including database and configuration files
  5. 5. Test the upgrade in a non-production environment first to verify compatibility
  6. 6. Perform the upgrade to the appropriate fixed version (2025.0.7+ or 2025.1.3+) following vendor instructions
  7. 7. After upgrade, verify the MOVEit Transfer Audit User module is functioning correctly
  8. 8. Confirm the version number has been updated correctly post-upgrade
Caveat Review release notes for any configuration or feature changes between versions that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8800 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8800 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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