dbcve.org
Ruckus Smartzone FirmwareOperating system · Commscope

CVE-2025-44960

HIGH · 8.8 CVSS v3.1 Published 2025-08-04
Fix available
A fix is available. Upgrade to 4.5.0.51 / 6.1.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RUCKUS SmartZone wireless controller versions prior to 6.1.2p3 Refresh Build contain an OS command injection vulnerability in a specific API route parameter. An attacker with access to the API can inject arbitrary OS commands, potentially achieving full system compromise with the privileges of the web service.

MitigationUpgrade SmartZone to version 6.1.2p3 Refresh Build or later. Until patched, restrict network access to the management interface using network segmentation and firewall rules.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ruckus Smartzone FirmwareOperating system
Affected:< 6.1.2= 6.1.2= 7.0.0= 7.1.0
Ruckus Network DirectorApplication
Affected:< 4.5.0.51

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product
    Determine whether the system runs RUCKUS SmartZone controller or Ruckus Network Director. Check the product name in the web UI or system information page.
    Affected if The product is SmartZone or Network Director.
  2. Check SmartZone firmware version
    Locate the firmware version in the SmartZone admin interface (typically under Administration > System > Firmware or a similar system information section). Compare the version string to the affected ranges: < 6.1.2, = 6.1.2, = 7.0.0, = 7.1.0.
    Affected if The installed version is 6.1.2, 7.0.0, 7.1.0, or any version lower than 6.1.2.
  3. Check Network Director version
    Locate the version information in the Ruckus Network Director admin interface (typically shown on the login page, dashboard, or under system settings). Compare to the affected range: < 4.5.0.51.
    Affected if The installed version is lower than 4.5.0.51.
  4. Verify API accessibility
    Determine if the SmartZone API interface (typically ports 8443 or 443) is reachable from untrusted networks. Review firewall rules, ACLs, and network segmentation around the management interface.
    Affected if The API endpoint is exposed to the internet or untrusted internal networks without proper access controls.

The environment is affected if it runs SmartZone versions 6.1.2, 7.0.0, or 7.1.0 (or any version below 6.1.2), or Network Director versions below 4.5.0.51, AND the API interface is accessible to an attacker.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.5.0.51 / 6.1.2 or later
Fixed in 4.5.0.516.1.2
Interim mitigation

Upgrade SmartZone to version 6.1.2p3 Refresh Build or later. Until patched, restrict network access to the management interface using network segmentation and firewall rules.

Recommended fix High confidence

Ruckus SmartZone: 6.1.2p3 Refresh Build; Ruckus Network Director: 4.5.0.51 or later

  1. 1. Identify the current firmware version of the Ruckus SmartZone controller by accessing the admin interface or using CLI commands
  2. 2. For SmartZone: If running version 6.1.2, 7.0.0, or 7.1.0, upgrade to 6.1.2p3 Refresh Build (or a later patched version if available)
  3. 3. For SmartZone: If running a version earlier than 6.1.2, upgrade directly to 6.1.2p3 Refresh Build or the latest stable release
  4. 4. For Ruckus Network Director: Upgrade to version 4.5.0.51 or later
  5. 5. After upgrading, verify the version change in the admin interface
  6. 6. Test that the API functionality still works normally post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruckus Smartzone Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-44960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-44960 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data