# CVE-2023-7338: Ruckus Unleashed Authenticated RCE in Gateway Mode

> Authenticated attackers can execute arbitrary code on Ruckus Unleashed access points via the web interface when gateway mode is enabled.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-pm6g-73h3-xpjp

## What is CVE-2023-7338?

CVE-2023-7338 is a high-severity command injection vulnerability in RUCKUS H350, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Ruckus Unleashed contains a remote code execution vulnerability in the web-based management interface that allows authenticated remote attackers to execute arbitrary code on the system when gateway mode is enabled. Attackers can exploit this vulnerability by sending specially crafted requests through the management interface to achieve arbitrary code execution on affected systems.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2023-7338 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7338 is a high-severity command injection vulnerability in RUCKUS H350, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7338 in the wild and no public exploit code.

Affected product: RUCKUS H350. 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-7338/ (Markdown: https://insights.sbomify.com/CVE-2023-7338/index.md)
```

## Sources

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

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