Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Apr 2022.
Rv132w FirmwareOperating system · Cisco

CVE-2018-0125

CRITICAL · 9.8 CVSS v3.1 Published 2018-02-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a critical input validation vulnerability in the web interface of Cisco RV132W and RV134W VPN routers. An unauthenticated remote attacker can send a crafted HTTP request with malicious input to achieve arbitrary code execution as the root user, gaining full control of the affected device or causing a DoS condition via system reload.

MitigationUpdate the firmware on affected Cisco RV132W and RV134W routers to version 1.0.1.11 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Rv132w FirmwareOperating system
Affected:= 1.0
Rv134w FirmwareOperating system
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the device web interface or check the device label/menu to confirm the model number is Cisco RV132W or RV134W.
    Affected if Model is RV132W or RV134W.
  2. Check firmware version
    Log into the router web interface and navigate to the Status or System Summary page to view the installed firmware version. Alternatively, check via CLI using 'show version' or similar command if SSH/telnet access is available.
    Affected if Firmware version is exactly 1.0.
  3. Verify web interface is enabled
    Check the router configuration to confirm the HTTP/HTTPS web management interface is enabled. This is typically found under Administration > Remote Management or similar settings.
    Affected if Web management interface is accessible and enabled.
  4. Assess network exposure
    Determine if the router web interface is reachable from untrusted networks by checking WAN-side accessibility or firewall rules.
    Affected if The web management interface is exposed to the internet or untrusted networks.

The device is affected if it is a Cisco RV132W or RV134W router running firmware version 1.0 with the web interface enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the firmware on affected Cisco RV132W and RV134W routers to version 1.0.1.11 or later to remediate this vulnerability.

Recommended fix High confidence

Firmware version 1.0.1.11 for Cisco RV132W ADSL2+ Wireless-N VPN Router and RV134W VDSL2 Wireless-AC VPN Router

  1. Download firmware version 1.0.1.11 for the affected Cisco router model (RV132W or RV134W) from the official Cisco website
  2. Access the router's web management interface via a browser
  3. Navigate to the Administration or Firmware Upgrade section
  4. Upload and apply the firmware version 1.0.1.11 file
  5. Allow the device to complete the upgrade process without interruption
  6. After the router reboots, verify the firmware version is now 1.0.1.11
Caveat Standard firmware upgrade risk - ensure stable power during upgrade process to avoid device corruption

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rv132w Firmware Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-0125 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-0125 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data