# CVE-2019-1827: Cisco Small Business RV320 and RV325 Routers Online Help Reflected Cross-Site Scripting Vulnerability

> An unauthenticated remote attacker can execute arbitrary script code or access sensitive browser information via a reflected XSS vulnerability in the router's Online Help service.

- **Severity:** Medium 6.1 (`CVSS:3.0/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:** 4 Apr 2019
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-82x3-cxj5-262m

## What is CVE-2019-1827?

CVE-2019-1827 is a medium-severity cross-site scripting vulnerability in Cisco Rv320 Firmware, published on 4 Apr 2019. 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 vulnerability in the Online Help web service of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the service. The vulnerability exists because the Online Help web service of an affected device insufficiently validates user-supplied input. An attacker could exploit this vulnerability by persuading a user of the service to click a malicious link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected service or access sensitive browser-based information.This vulnerability affects Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers running firmware releases prior to 1.4.2.22.

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

## Which versions are affected by CVE-2019-1827?

It affects 2 products.


Products: Cisco Rv320 Firmware, Cisco Rv325 Firmware.

## How do I fix CVE-2019-1827?

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

## Is CVE-2019-1827 being exploited?

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

## Other vulnerabilities in Cisco Rv320 Firmware

- [CVE-2019-1653](https://insights.sbomify.com/CVE-2019-1653/): Cisco Small Business RV320 and RV325 Routers Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2019-1652](https://insights.sbomify.com/CVE-2019-1652/): Cisco Small Business Routers Improper Input Validation (high 7.2, exploited in the wild)
- [CVE-2023-20117](https://insights.sbomify.com/CVE-2023-20117/): Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2023-20128](https://insights.sbomify.com/CVE-2023-20128/): Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers Command Injection Vulnerabilities (high 7.2)
- [CVE-2019-1828](https://insights.sbomify.com/CVE-2019-1828/): Cisco Small Business RV320 and RV325 Routers Weak Credential Encryption Vulnerability (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1827 and fix it if it is affected.

What it is: CVE-2019-1827 is a medium-severity cross-site scripting vulnerability in Cisco Rv320 Firmware, published on 4 Apr 2019. 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-2019-1827 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-2019-1827/ (Markdown: https://insights.sbomify.com/CVE-2019-1827/index.md)
```

## Sources

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

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