# CVE-2025-46123: Code injection in n/a

> An authenticated attacker can achieve remote code execution on Ruckus wireless controllers by exploiting a format string vulnerability in the guest password configuration endpoint.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-5jcw-5gh7-q3j5

## What is CVE-2025-46123?

CVE-2025-46123 is a high-severity code injection vulnerability in n/a, published on 21 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in CommScope Ruckus Unleashed prior to 200.15.6.212.14 and 200.17.7.0.139, and in Ruckus ZoneDirector prior to 10.5.1.0.279, where the authenticated configuration endpoint `/admin/_conf.jsp` writes the Wi-Fi guest password to memory with snprintf using the attacker-supplied value as the format string; a crafted password therefore triggers uncontrolled format-string processing and enables remote code execution on the controller.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2025-46123?

It affects 2 products.


Products: Ruckuswireless Ruckus Unleashed, Ruckuswireless Ruckus Zonedirector.

## How do I fix CVE-2025-46123?

No fix has been published for CVE-2025-46123 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-46123 being exploited?

There is no known exploitation of CVE-2025-46123 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-46120](https://insights.sbomify.com/CVE-2025-46120/): Path traversal in n/a (critical 9.8)
- [CVE-2025-46121](https://insights.sbomify.com/CVE-2025-46121/): Other in n/a (critical 9.8)
- [CVE-2025-46117](https://insights.sbomify.com/CVE-2025-46117/): Command injection in n/a (critical 9.1)
- [CVE-2025-46122](https://insights.sbomify.com/CVE-2025-46122/): Command injection in n/a (critical 9.1)
- [CVE-2025-46116](https://insights.sbomify.com/CVE-2025-46116/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46123 and fix it if it is affected.

What it is: CVE-2025-46123 is a high-severity code injection vulnerability in n/a, published on 21 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46123 in the wild and no public exploit code.

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-2025-46123/ (Markdown: https://insights.sbomify.com/CVE-2025-46123/index.md)
```

## Sources

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

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