nday
CVE-2025-31161

CrushFTP Authentication Bypass Vulnerability

CrushFTP / CrushFTP

Added to KEV 4 days after disclosure. nday has no fix record for it yet; that does not mean no patch exists. Listed by 2 of 4 PoC sources: exploitdb and nuclei.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

authentication bypass
CWE-305, stated by the CNA mitre and NVD, republishing [email protected]
remote, unauthenticated
AV:N, PR:N, UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA mitre
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA mitre
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA mitre
no user interaction
UI:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (CVSS 3.1) from the CNA mitre
ransomware use
CISA KEV entry: knownRansomwareCampaignUse is Known
Exploit-DB
Exploit-DB entries 52295
nuclei
nuclei templates CVE-2025-31161
stage
KEV
disclosed
disclosure → PoC
T+45d POC is date-only
cvss
9.8 CRITICAL v3.1
KEV due date
2025-04-28

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-04-03T00:00Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
2025-05-18, date only
nuclei
ITWexploited
≤ 2025-04-07, inferred from KEV
KEVKEV
2025-04-07, date only

Summary

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.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:N
None: no action by anyone other than the attacker

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

CVSS 3.1 vector from the CVE record, scored by the CNA mitre.

Event log

+DISdisclosed

CVE record published by mitre. CVSS 9.8, critical. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17624,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-31161",
  "occurred_at": "2025-04-03T00:00:00Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-31161",
      "date_added": "2025-04-07"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 9.8,
      "base_severity": "CRITICAL"
    },
    "ssvc": {
      "timestamp": "2025-08-15T19:11:52.009095Z",
      "automatable": "yes",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2025-04-03T00:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}
2025-04-07date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2025-04-28. Known to be used in ransomware campaigns.

src kev · nday , bulk import · raw
{
  "id": 465,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2025-04-07T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-305"
    ],
    "notes": "https://www.crushftp.com/crush11wiki/Wiki.jsp?page=Update ; https://nvd.nist.gov/vuln/detail/CVE-2025-31161",
    "product": "CrushFTP",
    "due_date": "2025-04-28",
    "precision": "day",
    "date_added": "2025-04-07",
    "vendor_project": "CrushFTP",
    "forensic_triage": "No",
    "required_action": "Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.",
    "vulnerability_name": "CrushFTP Authentication Bypass Vulnerability",
    "known_ransomware_campaign_use": "Known"
  }
}
≤ 2025-04-07inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

2025-05-18date only, from source
+POCpublic PoC

Exploit-DB lists public exploit code “CrushFTP 11.3.1 - Authentication Bypass” (EDB-52295).

src exploitdb 52295 · nday , bulk import · raw
{
  "id": 26926,
  "type": "poc_published",
  "source": "exploitdb",
  "url": "https://www.exploit-db.com/exploits/52295",
  "occurred_at": "2025-05-18T00:00:00Z",
  "observed_at": "2026-11-12T15:24:40.221206Z",
  "is_backfill": true,
  "dedupe_key": "52295",
  "detail": {
    "url": "https://www.exploit-db.com/exploits/52295",
    "file": "exploits/multiple/remote/52295.py",
    "kind": "exploit",
    "tags": [],
    "type": "remote",
    "title": "CrushFTP 11.3.1 - Authentication Bypass",
    "author": "İbrahimsql",
    "edb_id": 52295,
    "cve_ids": [
      "CVE-2025-31161"
    ],
    "platform": "multiple",
    "verified": false,
    "precision": "day",
    "confidence": "curated",
    "date_added": "2025-05-18",
    "date_updated": "2025-05-18",
    "date_published": "2025-05-18"
  }
}
time unknownsource gave no time
+POCpublic PoC

Nuclei has detection template CVE-2025-31161 (CrushFTP - Authentication Bypass). The source gives no release time for the template.

src nuclei · nday , bulk import · raw
{
  "id": 56756,
  "type": "poc_published",
  "source": "nuclei",
  "url": "https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-31161.yaml",
  "occurred_at": null,
  "observed_at": "2026-11-12T15:24:53.738369Z",
  "is_backfill": true,
  "dedupe_key": "CVE-2025-31161",
  "detail": {
    "url": "https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2025/CVE-2025-31161.yaml",
    "kind": "detection_template",
    "title": "CrushFTP - Authentication Bypass",
    "severity": "critical",
    "confidence": "curated",
    "cvss_score": "9.8",
    "template_id": "CVE-2025-31161",
    "template_path": "http/cves/2025/CVE-2025-31161.yaml"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.