dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-60105

HIGH · 8.6 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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 before 2.14.5 contains a server-side request forgery vulnerability in the fetchRemoteFile action caused by an incomplete IP blocklist check in the isBlockedIP() function, which fails to detect embedded IPv4 addresses within IPv4-mapped IPv6 addresses. An unauthenticated attacker can obtain a CSRF token from the public getSystemVars endpoint and submit a fetchRemoteFile request with a source URL resolving to an IPv4-mapped address, causing the server to issue HTTP requests to internal services and write responses to an attacker-controlled FTP destination, enabling retrieval of cloud instance metadata credentials.

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 before 2.14.5 has an SSRF vulnerability in the fetchRemoteFile action where the isBlockedIP() function fails to detect IPv4 addresses embedded in IPv4-mapped IPv6 addresses (e.g., ::ffff:192.168.1.1). Attackers obtain a CSRF token from the public getSystemVars endpoint, then use fetchRemoteFile to make the server request internal URLs that resolve to these mapped IPv4 addresses, enabling access to cloud metadata services.

MitigationUpgrade to Monsta FTP 2.14.5 or later, which includes proper validation of IPv4-mapped IPv6 addresses in the isBlockedIP() function to prevent SSRF bypasses.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Changed
Confidentiality
High
Integrity
None
Availability
None

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

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. Check Monsta FTP version
    Locate the version number in the software (typically in the footer, about page, or version file in the installation directory). Compare it to the affected range: any version before 2.14.5 is vulnerable.
    Affected if The installed version is below 2.14.5 (e.g., 2.14.4, 2.14.0, 2.10.x, etc.)
  2. Confirm fetchRemoteFile action is enabled
    Verify that the fetchRemoteFile action is accessible in the Monsta FTP application. This is typically found in the file transfer or remote download features accessible to authenticated users.
    Affected if fetchRemoteFile action is available and accessible to users (no disabled/enabled toggle found in public documentation, so this is the default state)
  3. Verify network accessibility to internal services
    Check if the server running Monsta FTP has network access to internal resources (e.g., localhost, 192.168.x.x, 10.x.x.x, cloud metadata endpoints like 169.254.169.254) that could be targeted via the SSRF.
    Affected if The Monsta FTP server can make outbound HTTP/HTTPS requests to internal network addresses or cloud metadata services
  4. Confirm getSystemVars endpoint is accessible
    Verify the getSystemVars public endpoint exists and returns a CSRF token without authentication. This is required for attackers to forge requests.
    Affected if The getSystemVars endpoint is publicly accessible and returns a valid CSRF token that can be harvested

You are affected if you run any Monsta FTP version before 2.14.5 and the fetchRemoteFile feature is accessible to users who can obtain a CSRF token from the getSystemVars endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Monsta FTP 2.14.5 or later, which includes proper validation of IPv4-mapped IPv6 addresses in the isBlockedIP() function to prevent SSRF bypasses.

Recommended fix Moderate confidence

Monsta FTP 2.14.5

  1. Confirm the current Monsta FTP installation version by accessing the admin interface or checking the application's version file
  2. Download Monsta FTP version 2.14.5 or later from the official vendor website (www.monstaftp.com)
  3. Before upgrading, backup the current installation including configuration files, user data, and database if applicable
  4. Deploy version 2.14.5 following the vendor's standard upgrade procedure
  5. Verify the upgrade was successful by checking the new version number in the admin interface
  6. Test that the fetchRemoteFile functionality works correctly with normal URLs
  7. Confirm that the isBlockedIP() function now properly blocks IPv4-mapped IPv6 addresses (e.g., ::ffff:192.168.1.1)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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