basicsecurity.net
Proof, not just disclosure.
Threats / Accellion / CVE-2021-27103
CVE-2021-27103 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Accellion FTA vulnerability

Accellion FTA contains a server-side request forgery vulnerability in wmProgressstat.html exploited via crafted POST requests. The flaw has been weaponized in ransomware campaigns.

Verdict

Today item, not a backlog item.

SSRF in Accellion FTA enables attackers to forge requests from the server to internal or external systems, facilitating reconnaissance, lateral movement, and data exfiltration. Active exploitation in ransomware operations confirms real-world threat.

CISA KEV Yes · 2021-11-033Ransomware use Flagged3EPSS 0.11406 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
21 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.11406 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Accellion, FTA. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-918 Server-Side Request Forgery (SSRF).CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious POST request to wmProgressstat.html that causes the FTA server to make requests to internal systems or external targets on my behalf.
Business
Attackers gain unauthorized access to internal network resources and sensitive data, leading to compromise of confidential information and operational disruption.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I use the SSRF to probe internal network topology, enumerate services, and identify additional targets for lateral movement within the victim environment.
Business
The organization faces expanded attack surface as internal systems become exposed to compromise, increasing risk of widespread infrastructure takeover.
3

Lateral reach — past segmentation narrative 3

Attacker
I leverage the compromised FTA server as a pivot point to deploy ransomware payloads across the network, encrypting critical business data.
Business
Operations halt as ransomware spreads through the network, resulting in data loss, extortion demands, regulatory penalties, and severe reputational damage.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • 21 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.