dbcve.org
Rv130w Wireless N Multifunction Vpn Router FirmwareOperating system · Cisco

CVE-2016-1395

CRITICAL · 9.8 CVSS v3.0 Published 2016-06-19
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
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
The web-based management interface on Cisco RV110W devices with firmware before 1.2.1.7, RV130W devices with firmware before 1.0.3.16, and RV215W devices with firmware before 1.3.0.8 allows remote attackers to execute arbitrary code as root via a crafted HTTP request, aka Bug ID CSCux82428.

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

A command injection vulnerability in the web-based management interface of Cisco RV110W, RV130W, and RV215W routers allows remote unauthenticated attackers to execute arbitrary code with root privileges via specially crafted HTTP requests.

MitigationUpgrade firmware to version 1.2.1.7 or later for RV110W, 1.0.3.16 or later for RV130W, and 1.3.0.8 or later for RV215W. If immediate patching is not possible, disable the web management interface from untrusted networks.

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
Rv130w Wireless N Multifunction Vpn Router FirmwareOperating system
Affected:= 1.0.0.21= 1.0.1.3= 1.0.2.7
Rv215w Wireless N Vpn Router FirmwareOperating system
Affected:= 1.1.0.5= 1.1.0.6= 1.2.0.14= 1.2.0.15= 1.3.0.7
Rv110w Wireless N Vpn Firewall FirmwareOperating system
Affected:= 1.1.0.9= 1.2.0.9= 1.2.0.10= 1.2.1.4

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.0/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. Check installed firmware version on Cisco RV110W
    Access the router web interface and navigate to Status > System Summary, or use SNMP/CLI to retrieve the firmware version. The firmware version is displayed as a number like 1.2.0.10.
    Affected if The installed version matches one of these: 1.1.0.9, 1.2.0.9, 1.2.0.10, or 1.2.1.4
  2. Check installed firmware version on Cisco RV130W
    Access the router web interface and navigate to Status > System Summary, or use SNMP/CLI to retrieve the firmware version. The firmware version is displayed as a number like 1.0.1.3.
    Affected if The installed version matches one of these: 1.0.0.21, 1.0.1.3, or 1.0.2.7
  3. Check installed firmware version on Cisco RV215W
    Access the router web interface and navigate to Status > System Summary, or use SNMP/CLI to retrieve the firmware version. The firmware version is displayed as a number like 1.2.0.15.
    Affected if The installed version matches one of these: 1.1.0.5, 1.1.0.6, 1.2.0.14, 1.2.0.15, or 1.3.0.7
  4. Verify web management interface is enabled
    Check router administration settings. On the RV110W, RV130W, and RV215W, go to Administration > Management and verify if HTTP/HTTPS management access is enabled. The vulnerability is exploitable through the web-based management interface.
    Affected if HTTP or HTTPS web management interface is enabled and accessible from untrusted networks

A router is affected if it runs any of the listed vulnerable firmware versions AND has the web-based management interface enabled, allowing remote unauthenticated attackers to inject commands via crafted HTTP requests.

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

Upgrade firmware to version 1.2.1.7 or later for RV110W, 1.0.3.16 or later for RV130W, and 1.3.0.8 or later for RV215W. If immediate patching is not possible, disable the web management interface from untrusted networks.

Recommended fix High confidence

RV110W: firmware 1.2.1.7 or later; RV130W: firmware 1.0.3.16 or later; RV215W: firmware 1.3.0.8 or later

  1. 1. Identify the exact Cisco VPN router model (RV110W, RV130W, or RV215W) from the affected device.
  2. 2. Access the device's web-based management interface and navigate to the Administration or System Settings section to confirm the current firmware version.
  3. 3. Visit the Cisco Software Download center at software.cisco.com and locate the firmware download page for your specific router model.
  4. 4. Download the appropriate fixed firmware version: RV110W upgrade to 1.2.1.7 or later; RV130W upgrade to 1.0.3.16 or later; RV215W upgrade to 1.3.0.8 or later.
  5. 5. In the device's web interface, locate the Firmware Upgrade or Upload New Firmware option (typically under Administration > Firmware Upgrade).
  6. 6. Upload the downloaded firmware file and allow the upgrade process to complete. Do not power off the device during the upgrade.
  7. 7. After the device reboots, verify the new firmware version is installed and test that VPN and wireless functionality are operational.
Caveat Ensure power continuity during firmware upgrade; backup configuration if possible as some settings may reset to defaults

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

Fix this in Rv130w Wireless N Multifunction Vpn Router Firmware Scoped from the published advisory
  • 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-2016-1395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-1395 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