dbcve.org
Moveit TransferApplication · Progress

CVE-2026-11903

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 2025.0.8 / 2025.1.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 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
Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Progress MOVEit Transfer (Ad Hoc module). This issue affects MOVEit Transfer: from 2026.0.0 before 2026.0.1, from 2025.1.0 before 2025.1.4, from 2025.0.0 before 2025.0.8.

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

A cross-site scripting (XSS) vulnerability in MOVEit Transfer's Ad Hoc module allows injection of malicious scripts through unsanitized user input that gets rendered in web pages without proper encoding or validation.

MitigationApply the vendor-provided patches: upgrade to 2026.0.1, 2025.1.4, or 2025.0.8 (or later) to remediate the XSS vulnerability.

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:<= 2024.1.8>= 2025.0.0, < 2025.0.8>= 2025.1.0, < 2025.1.4= 2026.0.0

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify installed MOVEit Transfer version
    Log into the MOVEit Transfer admin console and navigate to Help > About to view the exact version number, or query the version via the administrative interface or installation files if you have server access
    Affected if The installed version is <= 2024.1.8, OR >= 2025.0.0 and < 2025.0.8, OR >= 2025.1.0 and < 2025.1.4, OR equals 2026.0.0
  2. Confirm Ad Hoc module is enabled
    In the MOVEit Transfer admin interface, go to System Settings or Modules configuration and check whether the Ad Hoc module is currently enabled and available to users
    Affected if The Ad Hoc module is enabled and users can access it to create or share ad hoc transfers
  3. Verify web interface accessibility
    Confirm that the MOVEit Transfer web interface is accessible to users by checking IIS site bindings, internal network access, or reviewing which user groups have login permissions
    Affected if The MOVEit Transfer web interface is reachable by end users who can access the Ad Hoc module

You are affected if MOVEit Transfer runs an affected version AND the Ad Hoc module is enabled and accessible through the web interface, allowing unsanitized user input to be rendered in web pages.

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.8 / 2025.1.4 or later
Fixed in 2025.0.82025.1.4
Interim mitigation

Apply the vendor-provided patches: upgrade to 2026.0.1, 2025.1.4, or 2025.0.8 (or later) to remediate the XSS vulnerability.

Recommended fix High confidence

2026.0.1 (or 2025.1.4 or 2025.0.8 depending on current version)

  1. 1. Identify current MOVEit Transfer version by checking the application's help/about section or installation directory
  2. 2. Determine the appropriate upgrade target based on current version: if <=2024.1.8 upgrade to 2025.0.8 or later; if >=2025.0.0 and <2025.0.8 upgrade to 2025.0.8; if >=2025.1.0 and <2025.1.4 upgrade to 2025.1.4; if 2026.0.0 upgrade to 2026.0.1
  3. 3. Download the corresponding upgrade package from community.progress.com or official Progress downloads
  4. 4. Review upgrade documentation and release notes for pre-installation requirements
  5. 5. Perform a backup of the MOVEit Transfer database and configuration
  6. 6. Execute the upgrade following Progress MOVEit upgrade procedures
  7. 7. Verify the upgrade was successful and the Ad Hoc module functions correctly
Caveat Standard MOVEit upgrade procedures apply; test in non-production environment first

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

Fix this in Moveit Transfer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11903 — 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-11903 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