Skip to main content
CVE-2025-44960VulnerabilityPublished Updated

CVE-2025-44960: RUCKUS SmartZone · OS Command Injection

Affects RUCKUS SmartZoneSource CVE Database V5

0

Not known to be exploited · CVSS 8.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.8% chance of exploitation in 30 days – higher than 78% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
RUCKUS SmartZoneAffected
  • =0
Fixed in–

AI-suggested

1. Apply patches from RUCKUS as soon as they become available for SmartZone versions prior to 6.1.2p3 Refresh Build. Monitor vendor channels for updates. 2. Restrict access to the vulnerable API endpoints by implementing strict network segmentation and firewall rules to limit API exposure only to trusted management networks. 3. Enforce strong authentication and authorization controls on management interfaces to reduce the risk of unauthorized access. 4. Implement input validation and filtering at network perimeter devices or API gateways to detect and block suspicious command injection patterns. 5. Monitor logs and network traffic for unusual API requests or command execution patterns indicative of exploitation attempts. 6. Conduct regular vulnerability assessments and penetration testing focused on network management infrastructure to identify and remediate weaknesses. 7. Educate network administrators about the risks of command injection and the importance of timely patching and secure configuration. 8. Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures tuned to detect exploitation attempts targeting this vulnerability.

Description

RUCKUS SmartZone (SZ) before 6.1.2p3 Refresh Build allows OS command injection via a certain parameter in an API route.

References

Community reviews

Loading reviews…