# CVE-2019-1653: Cisco Small Business RV320 and RV325 Routers Information Disclosure

> Unauthenticated remote attackers can retrieve sensitive router configuration and diagnostic information via improper access controls in the web interface.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2019
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-j8w2-wx5p-fvx4

## What is CVE-2019-1653?

CVE-2019-1653 is a high-severity vulnerability in Cisco Rv320 Firmware, published on 24 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web-based management interface of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an unauthenticated, remote attacker to retrieve sensitive information. The vulnerability is due to improper access controls for URLs. An attacker could exploit this vulnerability by connecting to an affected device via HTTP or HTTPS and requesting specific URLs. A successful exploit could allow the attacker to download the router configuration or detailed diagnostic information. Cisco has released firmware updates that address this vulnerability.

Weakness: CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Cisco Rv320 Firmware, Cisco Rv325 Firmware.

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

No fix has been published for CVE-2019-1653 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2019-1653 being exploited?

Yes. Attackers have exploited CVE-2019-1653 in the wild since at least 3 Nov 2021.

Public exploit code:

- Just a PoC tool to extract password using CVE-2019-1653. (github_poc): https://github.com/shaheemirza/CiscoSpill
- NSE script to scan for Cisco routers vulnerable to CVE-2019-1653 (github_poc): https://github.com/dubfr33/CVE-2019-1653
- A vulnerability in the web-based management interface of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an unauthenticated, remote attacker to retrieve sensitive information. (github_poc): https://github.com/ibrahimzx/CVE-2019-1653
- Cisco RV320 and RV325 Unauthenticated Remote Code Execution (metasploit)
- Cisco RV320/RV326 Configuration Disclosure (metasploit)
- Cisco RV300 / RV320 - Information Disclosure (exploitdb)

## Other vulnerabilities in Cisco Rv320 Firmware

- [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-1827](https://insights.sbomify.com/CVE-2019-1827/): Cisco Small Business RV320 and RV325 Routers Online Help Reflected Cross-Site Scripting Vulnerability (medium 6.1)
- [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-1653 and fix it if it is affected.

What it is: CVE-2019-1653 is a high-severity vulnerability in Cisco Rv320 Firmware, published on 24 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2019-1653 in the wild since at least 3 Nov 2021.

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

## Sources

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

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