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 12 Aug 2025.
CrushftpApplication

CVE-2025-54309

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-18
Fix available
A fix is available. Upgrade to 10.8.5 / 11.3.4_23 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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
CrushFTP 10 before 10.8.5 and 11 before 11.3.4_23, when the DMZ proxy feature is not used, mishandles AS2 validation and consequently allows remote attackers to obtain admin access via HTTPS, as exploited in the wild in July 2025.

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

CrushFTP versions 10 before 10.8.5 and 11 before 11.3.4_23 contain a flaw in AS2 (Applicability Statement 2) validation logic. When the DMZ proxy feature is not in use, the validation can be bypassed, allowing unauthenticated remote attackers to obtain administrative access via HTTPS requests.

MitigationUpgrade CrushFTP to version 10.8.5 or 11.3.4_23 or later. If the DMZ proxy feature is not required, consider enabling it as a compensating control until the upgrade can be applied.

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.8.5>= 11.0.0, < 11.3.4_23

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 CrushFTP version
    Locate the installed CrushFTP version number in the admin web interface (typically on the login page or in System > Server Settings > General) or check the startup logs for the version string
    Affected if Version is 10.x before 10.8.5 or 11.x before 11.3.4_23
  2. Check DMZ proxy feature status
    Navigate to the CrushFTP admin interface and locate the DMZ proxy configuration settings (usually under Server Manager > DMZ Proxy or similar). Determine whether the DMZ proxy feature is currently enabled or disabled
    Affected if The DMZ proxy feature is disabled (not enabled)
  3. Confirm AS2 module usage
    Check if the AS2 (ASynchronous HTTPS-based data transfer) module or protocol is configured and in use on the CrushFTP server, typically found in Protocol Settings or Transfer Settings within the admin interface
    Affected if AS2 transfer functionality is configured and active on the server

You are affected if your installed CrushFTP version is 10.x before 10.8.5 or 11.x before 11.3.4_23 AND the DMZ proxy feature is not enabled, regardless of whether AS2 is actively used since the vulnerable validation logic is present in the codebase.

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.8.5 / 11.3.4_23 or later
Fixed in 10.8.511.3.4_23
Interim mitigation

Upgrade CrushFTP to version 10.8.5 or 11.3.4_23 or later. If the DMZ proxy feature is not required, consider enabling it as a compensating control until the upgrade can be applied.

Recommended fix High confidence

Upgrade to CrushFTP 10.8.5 (for 10.x branch) or 11.3.4_23 (for 11.x branch) or later

  1. 1. Identify the current CrushFTP version by checking the admin interface or running the version command
  2. 2. Create a complete backup of the CrushFTP configuration, users, and data directories
  3. 3. Download the appropriate fixed version from the official CrushFTP website (www.crushftp.com): version 10.8.5 for 10.x branch or version 11.3.4_23 for 11.x branch
  4. 4. Stop the CrushFTP service before upgrading
  5. 5. Install the new version following the standard upgrade procedure
  6. 6. Restart the CrushFTP service
  7. 7. Verify the version in the admin interface shows the updated release
  8. 8. Test that admin access works correctly and the AS2 validation functions properly
Caveat Standard upgrade - review release notes for any configuration changes between versions; ensure AS2 functionality is properly configured after upgrade

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

Fix this in Crushftp Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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