CVE-2021-27860
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 · uneditedA vulnerability in the web management interface of FatPipe WARP, IPVPN, and MPVPN software prior to versions 10.1.2r60p92 and 10.2.2r44p1 allows a remote, unauthenticated attacker to upload a file to any location on the filesystem. The FatPipe advisory identifier for this vulnerability is FPSA006.
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 confidenceUnauthenticated path traversal vulnerability in FatPipe WARP/IPVPN/MPVPN web management interface allows remote attackers to upload files to arbitrary filesystem locations. This file upload capability can likely be chained to achieve remote code execution by writing executable content to web-accessible directories.
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= 5.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2= 5.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2= 5.2.0= 6.1.2= 7.1.2= 9.1.2= 10.1.2= 10.2.2CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FatPipe product and firmware versionAccess the device console or use the web management interface to retrieve the firmware version. Typically found in the device status page, system information section, or via CLI command like 'fpversion' or 'show version'.Affected if The installed firmware version exactly matches any of these: 5.2.0, 6.1.2, 7.1.2, 9.1.2, 10.1.2, or 10.2.2 for any of the products (IPVPN, WARP, or MPVPN).
-
Confirm web management interface is accessibleVerify that the FatPipe web management interface (HTTP/HTTPS on ports 80 or 443, or custom ports) is reachable from the network. This can be tested with a browser or curl command targeting the device IP.Affected if The web management interface is exposed and accessible from a network where untrusted users could potentially reach it.
-
Check for unauthorized files in web root directoriesIf you have administrative access, inspect typical web upload directories on the device filesystem. Common locations may include /var/www/, /opt/fatpipe/, or the document root of the web server. Look for unexpected files with extensions like .php, .jsp, .sh, or .exe.Affected if Unexpected files exist in web-accessible directories that were not uploaded by legitimate administrators.
-
Review web server access logs for suspicious upload requestsExamine the web server access logs (typically found in /var/log/ or within the FatPipe device logs) for POST requests to upload endpoints. Look for patterns like multiple file uploads or uploads to unusual paths.Affected if Logs show unauthenticated or unexpected file upload requests, especially to paths outside normal upload directories.
A defender is affected if their FatPipe WARP, IPVPN, or MPVPN device runs firmware version 5.2.0, 6.1.2, 7.1.2, 9.1.2, 10.1.2, or 10.2.2 and has the web management interface accessible from an untrusted network.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to version 10.1.2r60p92 or 10.2.2r44p1 or later. Until patched, restrict network access to the web management interface using firewall rules or VPN access controls.
10.1.2r60p92 or 10.2.2r44p1 (or later)
- Backup the current FatPipe device configuration before initiating any upgrade.
- Schedule a maintenance window as the upgrade may require downtime.
- Download the firmware update from the official FatPipe support portal (www.fatpipeinc.com/support).
- Verify the firmware file integrity using checksums provided by FatPipe.
- Access the FatPipe web management interface or console.
- Navigate to the firmware upgrade section (typically under System or Administration menus).
- Upload and apply firmware version 10.1.2r60p92 or 10.2.2r44p1 (or later).
- Confirm the upgrade completes successfully and the device restarts.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-27860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-27860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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