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

Accellion FTA vulnerability

Accellion FTA contains a SQL injection vulnerability in document_root.html exploitable via crafted host headers. The vulnerability has been exploited in the wild and leveraged in ransomware campaigns.

Verdict

Today item, not a backlog item.

SQL injection in Accellion FTA allows unauthenticated attackers to inject malicious SQL through HTTP host headers, enabling unauthorized data access and modification. Active exploitation and ransomware deployment confirm high-severity real-world impact.

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

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
24 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.05998 — 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-89 SQL Injection, CWE-138 CWE-138 — weakness family: Injection.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 host header containing SQL syntax and send it to the document_root.html endpoint.
Business
Attackers gain unauthorized access to sensitive file transfer data stored in the FTA database.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute database queries to extract customer files, credentials, and metadata from the compromised system.
Business
Customer data and intellectual property are exfiltrated, creating breach notification and regulatory compliance obligations.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access by modifying database records or deploying web shells on the FTA server.
Business
Attackers maintain long-term presence for ransomware deployment or continued data theft operations.
4

Data at risk — exfiltration narrative 4

Attacker
I encrypt files on the compromised FTA infrastructure and demand ransom for decryption keys.
Business
Business operations halt; customers lose access to critical file transfer services and face extortion demands.
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)
  • 24 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.