# CVE-2023-49225: Cross-site scripting in AP Solo C110

> An attacker can execute arbitrary scripts in the browser of a user logging into Ruckus Access Point products, potentially compromising the session.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Dec 2023
- **Updated:** 28 May 2025
- **Also known as:** GHSA-34vj-g8wc-6443

## What is CVE-2023-49225?

CVE-2023-49225 is a medium-severity cross-site scripting vulnerability in CommScope, Inc. AP Solo C110, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A cross-site-scripting vulnerability exists in Ruckus Access Point products (ZoneDirector, SmartZone, and AP Solo). If this vulnerability is exploited, an arbitrary script may be executed on the web browser of the user who is logging in the product. As for the affected products/models/versions, see the information provided by the vendor listed under [References] section or the list under [Product Status] section.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 37 products.


Products: Ruckuswireless C110 Firmware, Ruckuswireless E510 Firmware, Ruckuswireless H320 Firmware, Ruckuswireless H350 Firmware, Ruckuswireless H510 Firmware, Ruckuswireless H550 Firmware, Ruckuswireless M510 Firmware, Ruckuswireless R310 Firmware, Ruckuswireless R320 Firmware, Ruckuswireless R350 Firmware, Ruckuswireless R510 Firmware, Ruckuswireless R550 Firmware, Ruckuswireless R560 Firmware, Ruckuswireless R610 Firmware, Ruckuswireless R650 Firmware, Ruckuswireless R710 Firmware, Ruckuswireless R720 Firmware, Ruckuswireless R730 Firmware, Ruckuswireless R750 Firmware, Ruckuswireless R760 Firmware and 17 more.

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

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

## Is CVE-2023-49225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-49225 is a medium-severity cross-site scripting vulnerability in CommScope, Inc. AP Solo C110, published on 7 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-49225 in the wild and no public exploit code.

Affected product: CommScope, Inc. AP Solo C110. 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-49225/ (Markdown: https://insights.sbomify.com/CVE-2023-49225/index.md)
```

## Sources

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

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