# CVE-2018-0125: Cisco VPN Routers Remote Code Execution

> Unauthenticated remote attackers can execute arbitrary code with root privileges or cause a denial of service via crafted HTTP requests to Cisco RV132W/RV134W routers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2018
- **Updated:** 14 Jan 2026
- **Also known as:** GHSA-4g9c-v6g6-3jgm

## What is CVE-2018-0125?

CVE-2018-0125 is a critical command injection vulnerability in Cisco RV132W and RV134W, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the web interface of the Cisco RV132W ADSL2+ Wireless-N VPN and RV134W VDSL2 Wireless-AC VPN Routers could allow an unauthenticated, remote attacker to execute arbitrary code and gain full control of an affected system, including issuing commands with root privileges. The attacker could also cause an affected system to reload, resulting in a denial of service (DoS) condition. The vulnerability is due to an incomplete input validation on user-controlled input in an HTTP request to the targeted device. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected system. A successful exploit could allow the attacker to execute arbitrary code as the root user and gain full control of the affected system or cause it to reload, resulting in a DoS condition. This vulnerability is fixed in firmware version 1.0.1.11 for the following Cisco products: RV132W ADSL2+ Wireless-N VPN Router and RV134W VDSL2 Wireless-AC VPN Router. Cisco Bug IDs: CSCvg92737, CSCvh60170.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-0125?

It affects 2 products.


Products: Cisco Rv132w Firmware, Cisco Rv134w Firmware.

## How do I fix CVE-2018-0125?

No fix has been published for CVE-2018-0125 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 15 Apr 2022.

## Is CVE-2018-0125 being exploited?

Yes. Attackers have exploited CVE-2018-0125 in the wild since at least 25 Mar 2022.

## Other vulnerabilities in Cisco RV132W and RV134W

- [CVE-2018-0127](https://insights.sbomify.com/CVE-2018-0127/): Missing authorization in Cisco RV132W and RV134W Wireless VPN Routers (critical 9.8)
- [CVE-2021-1251](https://insights.sbomify.com/CVE-2021-1251/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1308](https://insights.sbomify.com/CVE-2021-1308/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1309](https://insights.sbomify.com/CVE-2021-1309/): Cisco Small Business RV Series Routers Link Layer Discovery Protocol Vulnerabilities (high 7.4)
- [CVE-2021-1287](https://insights.sbomify.com/CVE-2021-1287/): Command injection in Cisco Small Business RV Series Router Firmware (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0125 and fix it if it is affected.

What it is: CVE-2018-0125 is a critical command injection vulnerability in Cisco RV132W and RV134W, published on 8 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-0125 in the wild since at least 25 Mar 2022.

Affected product: Cisco RV132W and RV134W. 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-2018-0125/ (Markdown: https://insights.sbomify.com/CVE-2018-0125/index.md)
```

## Sources

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

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