# CVE-2023-20139: Cisco Small Business RV016, RV042, RV042G, RV082 , RV320, and RV325 Routers Cross-Site Scripting Vulnerabilities

> Unauthenticated attackers can execute arbitrary scripts or steal browser data via XSS in Cisco Small Business Router web interfaces.

- **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:** 5 Apr 2023
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-4c54-m5m2-vq74

## What is CVE-2023-20139?

CVE-2023-20139 is a medium-severity cross-site scripting vulnerability in Cisco Rv320 Firmware, published on 5 Apr 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

Multiple vulnerabilities in the web-based management interface of Cisco Small Business RV016, RV042, RV042G, RV082, RV320, and RV325 Routers could allow an unauthenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface. These vulnerabilities are due to insufficient input validation by the web-based management interface. An attacker could exploit these vulnerabilities by sending crafted HTTP requests to an affected device and then persuading a user to visit specific web pages that include malicious payloads. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. Cisco has not released software updates that address these vulnerabilities.

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

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

It affects 6 products.


Products: Cisco Rv016 Firmware, Cisco Rv042 Firmware, Cisco Rv042g Firmware, Cisco Rv082 Firmware, Cisco Rv320 Firmware, Cisco Rv325 Firmware.

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

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

## Is CVE-2023-20139 being exploited?

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

## Other vulnerabilities in Cisco Rv320 Firmware

- [CVE-2023-20118](https://insights.sbomify.com/CVE-2023-20118/): Cisco Small Business RV Series Routers Command Injection (medium 6.5, exploited in the wild)
- [CVE-2023-20025](https://insights.sbomify.com/CVE-2023-20025/): Auth bypass in Cisco Small Business RV Series Router Firmware (critical 9.0)
- [CVE-2020-3274](https://insights.sbomify.com/CVE-2020-3274/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2020-3275](https://insights.sbomify.com/CVE-2020-3275/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2020-3276](https://insights.sbomify.com/CVE-2020-3276/): Cisco Small Business RV Series Routers Command Injection Vulnerabilities (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-20139 is a medium-severity cross-site scripting vulnerability in Cisco Rv320 Firmware, published on 5 Apr 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-20139 in the wild and no public exploit code.

Affected product: Cisco Rv320 Firmware. 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-20139/ (Markdown: https://insights.sbomify.com/CVE-2023-20139/index.md)
```

## Sources

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

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