dbcve.org
Monsta FtpApplication · Monstaftp

CVE-2020-14056

CRITICAL · 9.8 CVSS v3.1 Published 2020-07-01
Fix available
A fix is available. Upgrade to after 2.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Monsta FTP 2.10.1 or below is prone to a server-side request forgery vulnerability due to insufficient restriction of the web fetch functionality. This allows attackers to read arbitrary local files and interact with arbitrary third-party services.

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

Monsta FTP 2.10.1 and below contains an SSRF vulnerability in its web fetch functionality. Attackers can abuse the insufficiently restricted feature to make the server request arbitrary URLs, including file:// schemas to read local files from the server and internal network resources.

MitigationUpgrade to a version above 2.10.1. If immediate patching is not possible, disable or restrict access to the web fetch functionality and implement network segmentation to limit server-side access to internal resources.

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
Monsta FtpApplication
Affected:<= 2.10.1

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. Identify Monsta FTP installation version
    Locate the version file or check the main application header/footer for the version number. Common paths include version.php, footer.php, or the main index file where the version is displayed.
    Affected if The installed version is 2.10.1 or lower.
  2. Locate the web fetch functionality
    Search for files related to web fetching, URL fetching, or remote file access features. Look for scripts named similarly to fetch.php, webfetch.php, geturl.php, or functions handling URL parameters like 'url', 'fetch', or 'remote'.
    Affected if The web fetch feature exists in the installation.
  3. Verify web fetch feature accessibility
    Check if the web fetch script is accessible via HTTP/HTTPS without authentication or with low-privilege access. Test if parameters accepting URLs are present and processing requests.
    Affected if The web fetch endpoint is reachable without proper access restrictions.
  4. Check for file:// protocol handling
    Review the web fetch code to see if it includes logic to handle or restrict URL schemes. Look for any validation that prevents file://, gopher://, or other local/alternative protocols.
    Affected if The code lacks proper URL scheme validation and allows file:// requests.

You are affected if your Monsta FTP installation is version 2.10.1 or below and the web fetch feature is present and accessible, as this combination allows remote attackers to make the server request arbitrary URLs including local files.

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 a release after 2.10.1
Interim mitigation

Upgrade to a version above 2.10.1. If immediate patching is not possible, disable or restrict access to the web fetch functionality and implement network segmentation to limit server-side access to internal resources.

Recommended fix Moderate confidence

Latest available version on www.monstaftp.com (check for version > 2.10.1)

  1. 1. Navigate to the official Monsta FTP website (www.monstaftp.com) or the GitHub repository to check for the latest available version.
  2. 2. Download the latest stable release of Monsta FTP.
  3. 3. Before upgrading, perform a complete backup of your current Monsta FTP installation, including configuration files and user data.
  4. 4. Deploy the latest version in a staging environment and verify that all existing functionality works correctly.
  5. 5. Apply the upgrade to your production environment following standard change management procedures.
  6. 6. After upgrading, verify that the SSRF vulnerability is remediated by testing the web fetch functionality with controlled inputs.
Caveat Review release notes for any breaking changes between 2.10.1 and the target version

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

Fix this in Monsta Ftp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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