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 1 May 2024.
CrushftpApplication

CVE-2024-4040

CRITICAL · 10.0 CVSS v3.1 Published 2024-04-22
Fix available
A fix is available. Upgrade to 10.7.1 / 11.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

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
A server side template injection vulnerability in CrushFTP in all versions before 10.7.1 and 11.1.0 on all platforms allows unauthenticated remote attackers to read files from the filesystem outside of the VFS Sandbox, bypass authentication to gain administrative access, and perform remote code execution on the server.

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

This is a server-side template injection (SSTI) vulnerability in CrushFTP affecting all versions before 10.7.1 and 11.1.0. The vulnerability allows unauthenticated remote attackers to escape the VFS sandbox, read arbitrary files from the filesystem, bypass authentication to gain administrative access, and achieve remote code execution on the server.

MitigationUpgrade CrushFTP to version 10.7.1 or 11.1.0 or later immediately. If patching cannot be performed quickly, restrict network access to the CrushFTP service to prevent unauthenticated 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
CrushftpApplication
Affected:>= 10.0.0, < 10.7.1>= 11.0.0, < 11.1.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 CrushFTP installation
    Look for CrushFTP directories (commonly /opt/CrushFTP12/ on Linux or C:\CrushFTP12\ on Windows) or check running services for CrushFTP processes
    Affected if CrushFTP software is present on the system
  2. Identify installed version
    Check the web interface login page for the version number, or examine the crushftp.config/prefs.xml configuration file in the installation directory for a version attribute
    Affected if The installed version falls within 10.0.0 to 10.7.0 (inclusive) or 11.0.0 to 11.1.0 (exclusive)
  3. Verify web interface accessibility
    Check if the CrushFTP web interface (default ports 8080, 8443, or 80/443) is reachable from the network
    Affected if The management interface is network-accessible (this is required for unauthenticated exploitation)
  4. Inspect for unauthorized access indicators
    Review CrushFTP access logs for unusual requests to template endpoints, unexpected authentication bypass events, or administrative actions from unauthenticated sources
    Affected if Logs show template injection patterns or authentication bypass activity

You are affected if CrushFTP versions 10.0.0-10.7.0 or 11.0.0-11.1.0 are running with an exposed web interface, since the SSTI flaw allows unauthenticated remote attackers to bypass authentication and execute code.

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 10.7.1 / 11.1.0 or later
Fixed in 10.7.111.1.0
Vendor patch www.crushftp.com →
Interim mitigation

Upgrade CrushFTP to version 10.7.1 or 11.1.0 or later immediately. If patching cannot be performed quickly, restrict network access to the CrushFTP service to prevent unauthenticated exploitation.

Recommended fix High confidence

CrushFTP 10.7.1 (for 10.x branches) or CrushFTP 11.1.0 (for 11.x branches)

  1. 1. Identify the currently running CrushFTP version in your environment
  2. 2. If running version 10.x (>= 10.0.0 and < 10.7.1), upgrade to version 10.7.1 or later
  3. 3. If running version 11.x (>= 11.0.0 and < 11.1.0), upgrade to version 11.1.0 or later
  4. 4. Download the appropriate updated version from the official CrushFTP download page
  5. 5. Apply the upgrade following CrushFTP's standard upgrade procedure
  6. 6. Verify the upgrade was successful and the service is running correctly
  7. 7. Confirm the vulnerability is no longer exploitable by reviewing system logs for any suspicious activity around the time of discovery

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

Fix this in Crushftp Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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