CVE Intelligence
High Cross-site scripting

CVE-2026-89069 — MOVEit Transfer Stored XSS Vulnerability in Ad Hoc Packages

Improper neutralization of input during web page generation ('cross-site scripting') vulnerability in Progress MOVEit Transfer (Ad Hoc module). This issue affects MOVEit Transfer: before 2025.1.6 and from 2026.0.0 before 2026.0.4.

Published Oct 14, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: ProgressSoftware

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+6
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.44%
ahead of 37% of scored CVEs · Oct 15, 2026
Affects
Progress
Moveit Transfer
CVSS base
8.0
High · 3 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Progress Moveit Transfer).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Progress Moveit Transfer < 2025.1.6≥ 2026.0.0 and < 2026.0.4 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.0 CVSS 3.1 High 2.1 5.9 security@progress.com via NIST National Vulnerability Database
8.0 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
8.0 CVSS 3.1 High — — ProgressSoftware via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H (score shown at the top: security@progress.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-79 · Cross-site Scripting (XSS)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor CSP violation reports and script payloads in reflected parameters.
web/proxy/WAF logsnetwork IDS/IPSapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Awaiting Analysis → Undergoing Analysis
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · Received → Awaiting Analysis
    Oct 15, 2026 · NIST National Vulnerability Database
  • Affected products added · progress/moveit transfer
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • CVSS changed · 8.0
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Received
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • CVE published
    Oct 14, 2026 · ProgressSoftware

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

3 on the record

Elsewhere on this site

Progress
every CVE for this vendor
CWE-79
other pages naming this weakness

Related CVEs (same products)

  • High CVE-2026-89077 MOVEit Transfer Identity validation flaw in SFTP authentication 1d
  • High CVE-2026-89074 MOVEit Transfer Email MFA Bypass 1d
  • High CVE-2026-89071 MOVEit Transfer LDAP injection in certificate-based authentication 1d
  • High CVE-2026-89072 MOVEit Transfer Authorization Flaw in Certificate Management 1d
  • High CVE-2026-89073 MOVEit Transfer Access restriction bypass in OAuth authentication 1d
  • High CVE-2026-89070 MOVEit Transfer OIDC Authentication Replay Vulnerability 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-89069 is "MOVEit Transfer Stored XSS Vulnerability in Ad Hoc Packages", rated High. It affects Moveit Transfer (Progress); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.0 describes technical severity. EPSS 0.44% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.