VulnerabilityPublished 15 Apr 2025Updated 3 Nov 2025

CVE-2025-32103: CrushFTP · Path Traversal: '\\UNC\share\name\'

Affects CrushFTPSource GCVE Database

Compare

Not known to be exploited · CVSS 5.0 Medium.

Data as of 30 Oct 2026, 00:15 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (mitre)	CVSS 3.1	5.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
CrushFTP CrushFTP	Affected =9 =11 >=10.0.0 <=10.8.4 >=11.0.0 <=11.3.1	Fixed in–

AI-suggested

Until a fix is available, restrict access to the /WebInterface/function/ URI and limit SMB share permissions to mitigate exposure.

Description

CVE-2025-32103 is a directory traversal vulnerability in CrushFTP versions 9.x, 10.x through 10.8.4, and 11.x through 11.3.1. It allows an attacker with limited privileges to access files on SMB UNC shares via the /WebInterface/function/ URI, bypassing SecurityManager restrictions. The vulnerability has a medium severity with a CVSS score of 5. No public exploits or patches are currently documented.

Impact

An attacker with low privileges can exploit this vulnerability to read arbitrary files accessible via SMB UNC shares, bypassing security restrictions. This leads to unauthorized information disclosure but does not allow modification or denial of service. There are no known exploits in the wild at this time.

Summary

CrushFTP versions 9.x, 10.x up to 10.8.4, and 11.x up to 11.3.1 contain a path traversal vulnerability (CWE-40) that enables an attacker to read files accessible through SMB UNC share pathnames by exploiting the /WebInterface/function/ URI. This bypasses the SecurityManager restrictions intended to prevent unauthorized file access. The vulnerability is network exploitable with low attack complexity and requires low privileges but no user interaction. It impacts confidentiality by allowing information disclosure but does not affect integrity or availability.

CWE-40Path Traversal: '\\UNC\share\name\' (Windows UNC Share) (opens in a new tab)
Variant weakness
The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 00:15 UTC

WeaknessesCWE-40

Technical details

References

Community reviews

Related threats