Skip to main content
No exploitation reportedFix available

CVE-2020-8612

No exploitation reported by the sources we read.

  • Published2020-02-14
  • Fixed in2019.2.1
  • WeaknessCWE-79

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

In Progress MOVEit Transfer 2019.1 before 2019.1.4 and 2019.2 before 2019.2.1, a REST API endpoint failed to adequately sanitize malicious input, which could allow an authenticated attacker to execute arbitrary code in a victim's browser, aka XSS.

Timeline

dates in UTC
  1. 2020-02-1419:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2020-8612?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2020-8612?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
MOVEit Transfer
BranchAffectedFixed in
2019.2≥ 2019.2, < 2019.2.12019.2.1
Progess moveit transfer
BranchAffectedFixed in
2019.1≥ 2019.1, < 2019.1.42019.1.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update MOVEit Transfer to 2019.2.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.19read 2026-10-23
  • NVDCVSS 2.06read 2026-10-23
  • NVDweakness (CWE)CWE-79read 2026-10-23
  • FIRST EPSSEPSS score1.7 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Published
2020-02-14
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2020-8612?

In Progress MOVEit Transfer 2019.1 before 2019.1.4 and 2019.2 before 2019.2.1, a REST API endpoint failed to adequately sanitize malicious input, which could allow an authenticated attacker to execute arbitrary code in a victim's browser, aka XSS.

Is CVE-2020-8612 actively exploited?

Active exploitation of CVE-2020-8612 has not been confirmed. Its EPSS score was 1.7% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2020-8612?

CVE-2020-8612 has a CVSS v3 base score of 9 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month