dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021. Known ransomware use
FtaApplication · Accellion

CVE-2021-27103

CRITICAL · 9.8 CVSS v3.1 Published 2021-02-16
Fix available
A fix is available. Upgrade to 9_12_416 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware Remotely reachable No privileges Zero-click

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
Accellion FTA 9_12_411 and earlier is affected by SSRF via a crafted POST request to wmProgressstat.html. The fixed version is FTA_9_12_416 and later.

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 · high confidence

Accellion FTA versions 9_12_411 and earlier contain a Server-Side Request Forgery (SSRF) vulnerability in the wmProgressstat.html endpoint. An unauthenticated attacker can craft a malicious POST request to cause the FTA server to make unauthorized requests to internal or external resources, potentially leading to exposure of internal services and data.

MitigationUpgrade Accellion FTA to version FTA_9_12_416 or later. Additionally, implement network segmentation and restrict outbound network access from the FTA server to minimize impact of potential SSRF exploitation.

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
FtaApplication
Affected:< 9_12_416

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm Accellion FTA is exposed
    Identify if the Accellion File Transfer Appliance web interface is accessible on your network by checking for FTA login pages or known FTA paths (e.g., /guest) on affected hosts
    Affected if FTA web interface is accessible from an untrusted network without proper segmentation
  2. Determine installed FTA version
    Log into the FTA admin interface and navigate to the System Information or About page to view the firmware version, or check the /etc/accellion-version file on the FTA server if you have shell access
    Affected if Installed version is 9_12_411 or earlier, or any version below 9_12_416
  3. Verify wmProgressstat.html endpoint accessibility
    Send a crafted POST request to the wmProgressstat.html endpoint (typically at /wmProgressstat.html) using curl or similar tool. The endpoint should respond if the vulnerability is present
    Affected if The endpoint accepts POST requests and returns a response indicating the request was processed, particularly if you observe the server making outbound HTTP requests to arbitrary URLs you control
  4. Check for evidence of SSRF exploitation
    Review FTA server logs (typically in /var/log/ or via the admin interface) for unusual outbound HTTP requests from the FTA server to internal services or unexpected external URLs, or monitor network traffic for unexpected outbound connections from the FTA server
    Affected if Log entries or network traffic show the FTA server making HTTP requests to internal resources (e.g., internal IPs, localhost, cloud metadata endpoints) or unusual external destinations that were not initiated by legitimate administrators

A user is affected if their Accellion FTA version is below 9_12_416 AND the wmProgressstat.html endpoint is accessible, as this combination allows unauthenticated attackers to trigger the SSRF vulnerability.

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 9_12_416 or later
Fixed in 9_12_416
Interim mitigation

Upgrade Accellion FTA to version FTA_9_12_416 or later. Additionally, implement network segmentation and restrict outbound network access from the FTA server to minimize impact of potential SSRF exploitation.

Recommended fix High confidence

FTA_9_12_416 or later

  1. 1. Identify the current Accellion FTA version by checking the system or admin interface
  2. 2. Download the FTA_9_12_416 or later version from the official Accellion support portal
  3. 3. Follow Accellion's documented upgrade procedure to install the updated version
  4. 4. Verify the upgrade was successful by checking the FTA version number
  5. 5. Test that the wmProgressstat.html endpoint no longer accepts malicious SSRF requests

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

Fix this in Fta Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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