dbcve.org
Ruckus UnleashedApplication · Ruckuswireless

CVE-2025-46120

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-21
Fix available
A fix is available. Upgrade to 10.5.1.0.279 / 200.15.6.212.14 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
An issue was discovered in CommScope Ruckus Unleashed prior to 200.15.6.212.27 and 200.18.7.1.323, and in Ruckus ZoneDirector prior to 10.5.1.0.282, where a path-traversal flaw in the web interface lets the server execute attacker-supplied EJS templates outside permitted directories, allowing a remote unauthenticated attacker who can upload a template (e.g., via FTP) to escalate privileges and run arbitrary template code on the controller.

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

A path-traversal vulnerability in the web interface of Ruckus Unleashed and ZoneDirector allows unauthenticated remote attackers to execute attacker-supplied EJS templates outside permitted directories. By uploading a malicious template via FTP and exploiting the path traversal flaw, an attacker can achieve privilege escalation and execute arbitrary code on the controller.

MitigationUpgrade to Ruckus Unleashed 200.15.6.212.27/200.18.7.1.323 or ZoneDirector 10.5.1.0.282 or later; restrict or disable FTP access and monitor for unauthorized template uploads.

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 UnleashedApplication
Affected:< 200.15.6.212.14>= 200.17, < 200.17.7.0.139
Ruckus ZonedirectorApplication
Affected:< 10.5.1.0.279

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Ruckus Unleashed version
    Log into the web UI and navigate to Administration > System, or run 'show version' via CLI. Locate the software version number displayed.
    Affected if Version is < 200.15.6.212.14 OR (>= 200.17 AND < 200.17.7.0.139)
  2. Identify installed Ruckus ZoneDirector version
    Log into the web UI and navigate to Administer > System, or run 'show version' via CLI. Locate the software version number displayed.
    Affected if Version is < 10.5.1.0.279
  3. Verify web interface is internet-facing
    Check network/firewall configurations to determine if the Ruckus web interface (TCP ports 80/443 or the configured HTTP/HTTPS port) is directly accessible from untrusted networks or the internet.
    Affected if Web management interface is exposed to untrusted networks (prerequisite for unauthenticated exploitation)
  4. Check for template upload or EJS template functionality
    In the web UI, look for sections related to 'Templates', 'EJS', 'Custom Views', or 'File Upload' under Administration, Wireless, or Network settings. Note if any template import or custom view feature is available without authentication.
    Affected if Template upload or EJS template functionality exists and is accessible (attack vector for path traversal)
  5. Review FTP and file transfer access controls
    Check under Administration > File Management or similar for FTP server settings, and verify if anonymous or unauthenticated FTP/template upload access is enabled.
    Affected if FTP or template upload is accessible to untrusted sources without proper authentication restrictions

Environment is affected if running a vulnerable Unleashed version (< 200.15.6.212.14 or >= 200.17 to < 200.17.7.0.139) or ZoneDirector version < 10.5.1.0.279, AND the web interface is exposed to untrusted networks with accessible template functionality.

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 10.5.1.0.279 / 200.15.6.212.14 / 200.17.7.0.139 or later
Fixed in 10.5.1.0.279200.15.6.212.14200.17.7.0.139
Interim mitigation

Upgrade to Ruckus Unleashed 200.15.6.212.27/200.18.7.1.323 or ZoneDirector 10.5.1.0.282 or later; restrict or disable FTP access and monitor for unauthorized template uploads.

Recommended fix High confidence

Ruckus Unleashed: 200.15.6.212.27 or later (for 200.15.x branch), or 200.18.7.1.323 or later (for 200.17.x/200.18.x branch); Ruckus ZoneDirector: 10.5.1.0.282 or later

  1. 1. Identify the currently deployed Ruckus Unleashed or ZoneDirector model and version using the web GUI (Dashboard > System) or CLI (show version command)
  2. 2. For Ruckus Unleashed: If running version 200.15.x, upgrade to 200.15.6.212.27 or later; if running version 200.17.x or 200.18.x, upgrade to 200.18.7.1.323 or later
  3. 3. For Ruckus ZoneDirector: Upgrade to version 10.5.1.0.282 or later
  4. 4. Download the appropriate firmware from support.ruckuswireless.com (login required)
  5. 5. Back up the current configuration via the web GUI (Maintenance > Backup & Restore > Download Configuration) or CLI (save config command)
  6. 6. Upload the new firmware via the web GUI (Maintenance > Firmware Upgrade > Upload Firmware) or CLI
  7. 7. After firmware upload completes, reboot the controller via the web GUI (Reboot) or CLI (reboot command)
  8. 8. Verify the upgrade was successful by checking the new version matches the expected fixed release
Caveat Review release notes for any configuration changes or feature modifications between versions; firmware upgrades may require brief controller downtime

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

Fix this in Ruckus Unleashed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-46120 — 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-46120 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