# CVE-2023-25717: Multiple Ruckus Wireless Products CSRF and RCE

> Unauthenticated attackers can execute arbitrary commands on Ruckus Wireless Admin devices via a crafted HTTP GET request.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 May 2023 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Feb 2023
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-53wx-2f9c-xxxr

## What is CVE-2023-25717?

CVE-2023-25717 is a critical command injection vulnerability in n/a, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ruckus Wireless Admin through 10.4 allows Remote Code Execution via an unauthenticated HTTP GET Request, as demonstrated by a /forms/doLogin?login_username=admin&password=password$(curl substring.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2023-25717?

It affects 3 products.


Products: Commscope Ruckus Smartzone Firmware, Ruckuswireless Ruckus Wireless Admin, Ruckuswireless Smartzone Ap.

## How do I fix CVE-2023-25717?

No fix has been published for CVE-2023-25717 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Jun 2023.

## Is CVE-2023-25717 being exploited?

Yes. Attackers have exploited CVE-2023-25717 in the wild since at least 12 May 2023.

Public exploit code:

- Ruckus Wireless Admin - Remote Code Execution (nuclei): http/cves/2023/CVE-2023-25717.yaml

## Other vulnerabilities in n/a

- [CVE-2025-44954](https://insights.sbomify.com/CVE-2025-44954/): Hardcoded credentials in SmartZone (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25717 and fix it if it is affected.

What it is: CVE-2023-25717 is a critical command injection vulnerability in n/a, published on 13 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2023-25717 in the wild since at least 12 May 2023.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-25717/ (Markdown: https://insights.sbomify.com/CVE-2023-25717/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-25717
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-25717
- OSV: https://osv.dev/vulnerability/CVE-2023-25717

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-25717/
Summaries are generated and may contain mistakes; the official description above is the record.