CVE-2025-44962VulnerabilityPublished 4 Aug 2025Updated 3 Nov 2025

CVE-2025-44962: RUCKUS SmartZone · Path Traversal: '../filedir'

Affects RUCKUS SmartZoneSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.0Medium

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

EPSS: 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

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.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC 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
RUCKUS SmartZone	Affected =0	Fixed in–

AI-suggested

1. Upgrade affected RUCKUS SmartZone devices to version 6.1.2p3 Refresh Build or later, where the vulnerability is patched. 2. Restrict access to SmartZone management interfaces to trusted networks and administrators only, using network segmentation and firewall rules. 3. Implement strong authentication and role-based access controls to limit user privileges, minimizing the risk from low-privilege accounts. 4. Monitor logs and audit access to detect any unusual file access patterns indicative of exploitation attempts. 5. If immediate patching is not possible, consider disabling or restricting features that accept file path inputs or applying web application firewalls (WAFs) with rules to block directory traversal sequences. 6. Conduct regular security assessments and penetration tests focusing on management interfaces to identify similar vulnerabilities. 7. Educate administrators about the risks of path traversal and the importance of timely updates.

Description

RUCKUS SmartZone (SZ) before 6.1.2p3 Refresh Build allows ../ directory traversal to read files.

Impact

For European organizations, the primary impact of CVE-2025-44962 is unauthorized disclosure of sensitive files on RUCKUS SmartZone devices. This could include configuration files, user credentials, or other sensitive operational data, which may lead to further compromise or espionage. Telecommunications providers, enterprises, and public sector entities relying on RUCKUS SmartZone for network management are at risk. Exposure of sensitive data could undermine confidentiality and trust, potentially leading to regulatory compliance issues under GDPR if personal data is involved. While the vulnerability does not directly affect system integrity or availability, the information gained could facilitate subsequent attacks. The medium severity score reflects the moderate risk, but the real-world impact depends on the sensitivity of the exposed files and the network segmentation protecting the management interfaces. Given the widespread use of RUCKUS products in Europe, especially in critical infrastructure and large enterprises, the threat is significant enough to warrant prompt remediation.

CWE-24Path Traversal: '../filedir' (opens in a new tab)
Variant weakness
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
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 4 Nov 2025, 01:25 UTC

WeaknessesCWE-24

Technical details

References

Community reviews

Related threats