LiveActive security incident?Get immediate response
CVE Record

CVE-2025-31161: CrushFTP 10 before 10.8.4 and 11 before 11.3.1 allows authentication bypass and takeover of the crushadmin...

CrushFTP 10 before 10.8.4 and 11 before 11.3.1 allows authentication bypass and takeover of the crushadmin account (unless a DMZ proxy instance is used), as exploited in the wild in March and April 2025, aka "Unauthenticated HTTP(S) port access." A race condition exists in the AWS4-HMAC (compatible with S3) authorization method of the HTTP component of the FTP server. The server first verifies the existence of the user by performing a call to login_user_pass() with no password requirement. This will authenticate the session through the HMAC verification process and up until the server checks for user verification once more. The vulnerability can be further stabilized, eliminating the need for successfully triggering a race condition, by sending a mangled AWS4-HMAC header. By providing only the username and a following slash (/), the server will successfully find a username, which triggers the successful anypass authentication process, but the server will fail to find the expected SignedHeaders entry, resulting in an index-out-of-bounds error that stops the code from reaching the session cleanup. Together, these issues make it trivial to authenticate as any known or guessable user (e.g., crushadmin), and can lead to a full compromise of the system by obtaining an administrative account.

CriticalCVSS 9.8Known exploitedUpdated
Glexia's TakeHuman reviewedcritical

Security readout for executives and security teams

Plain-English summary

CVE-2025-31161 lets an unauthenticated attacker bypass login on vulnerable CrushFTP servers and potentially take over the crushadmin account. The issue affects CrushFTP 10 before 10.8.4 and 11 before 11.3.1, with sources noting exploitation in March and April 2025.

Executive priority

Treat this as an urgent remediation item for any exposed CrushFTP deployment. It is critical severity, requires no credentials, affects administrative control, and is listed by CISA as known exploited.

Technical view

The flaw is in CrushFTP's HTTP component AWS4-HMAC S3-compatible authorization path. User existence is checked without requiring a password, and session cleanup can be avoided through the flawed authorization flow, allowing authentication as a known or guessable user such as crushadmin.

Likely exposure

Highest exposure is internet-accessible CrushFTP HTTP(S) service running version 10 before 10.8.4 or 11 before 11.3.1. The CVE text states DMZ proxy use changes exposure, but organizations should validate their exact deployment against vendor guidance.

Exploitation context

CISA KEV inclusion and the CVE description support active exploitation. Public sources describe in-the-wild exploitation during March and April 2025 and potential administrative takeover. The bundle does not prove every vulnerable instance was exploited.

Researcher notes

Evidence supports authentication bypass through the AWS4-HMAC authorization flow and possible account takeover. Avoid assuming exploitability solely from product presence; version, HTTP(S) exposure, and DMZ proxy architecture matter. Use vendor and CISA sources for final remediation deadlines and scope.

Mitigation direction

  • Upgrade CrushFTP 10 to 10.8.4 or later.
  • Upgrade CrushFTP 11 to 11.3.1 or later.
  • Review CrushFTP vendor vulnerability guidance for deployment-specific mitigations.
  • Restrict direct HTTP(S) exposure where vendor guidance supports that design.
  • Assess DMZ proxy configuration rather than assuming protection.

Validation and detection

  • Inventory all CrushFTP servers and record exact versions.
  • Confirm whether HTTP(S) access is internet-facing or internally restricted.
  • Verify any DMZ proxy deployment matches vendor guidance.
  • Review admin accounts, especially crushadmin, for unauthorized changes.
  • Check logs for suspicious authentication or administrative activity.
Prepared
Reviewed
Confidence
high
Sources
12

Michael Williams reviewed this cited source version on .

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-305: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-31161 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
11Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-31161Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CrushFTPCrushFTP10, 11unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-305 · source CWE mapping

Authentication Bypass by Primary Weakness

Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.