dbcve.org
Rv110w FirmwareOperating system · Cisco

CVE-2021-1215

HIGH · 7.2 CVSS v3.1 Published 2021-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Multiple vulnerabilities in the web-based management interface of Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers could allow an authenticated, remote attacker to execute arbitrary code or cause an affected device to restart unexpectedly. The vulnerabilities are due to improper validation of user-supplied input in the web-based management interface. An attacker could exploit these vulnerabilities by sending crafted HTTP requests to an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system or cause the device to reload, resulting in a denial of service (DoS) condition. To exploit these vulnerabilities, an attacker would need to have valid administrator credentials on the affected device. Cisco has not released software updates that address these vulnerabilities.

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

Authenticated command injection vulnerability in Cisco Small Business RV110W, RV130, RV130W, and RV215W router web management interfaces due to improper input validation. An attacker with valid administrator credentials can send crafted HTTP requests to execute arbitrary code with root privileges or cause device reload (DoS). No firmware patches available from Cisco.

MitigationSince no vendor patches exist, organizations should restrict web management interface access to trusted networks only, enforce strong administrator credentials, monitor for suspicious activity, and plan for replacement of affected devices.

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
Rv110w FirmwareOperating system
Affected:= 1.2.2.8= 1.3.1.7
Rv130 Vpn Router FirmwareOperating system
Affected:= 1.2.2.8= 1.3.1.7
Rv130w FirmwareOperating system
Affected:= 1.2.2.8= 1.3.1.7
Rv215w Wireless N Vpn Router FirmwareOperating system
Affected:= 1.2.2.8= 1.3.1.7
Application Extension PlatformPlugin / extension
Affected:= 1.0.3.55

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 the device model
    Access the router web management interface and navigate to Status, System Summary, or Device Info page to confirm the model number (RV110W, RV130, RV130W, or RV215W). For Application Extension Platform, check the device or software inventory.
    Affected if The device model is one of: RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform.
  2. Locate the firmware version
    In the web management interface, go to Administration, Firmware Upgrade, or Status page to view the installed firmware version. Alternatively, check the release notes or system information section.
    Affected if The firmware version is displayed on the device.
  3. Compare firmware version to affected versions
    Match the installed firmware version against the vulnerable versions: 1.2.2.8 or 1.3.1.7 for RV series routers, or 1.0.3.55 for Application Extension Platform.
    Affected if The installed firmware version is exactly 1.2.2.8, 1.3.1.7 (for RV series), or 1.0.3.55 (for Application Extension Platform).
  4. Verify web management interface accessibility
    Confirm whether the router web management interface (HTTP/HTTPS on ports 80 or 443, or custom management ports) is reachable from network segments. Check firewall rules, ACLs, or VPN configurations.
    Affected if The web management interface is exposed to untrusted networks (such as the internet or guest networks).

You are affected if your device is an RV110W, RV130, RV130W, RV215W, or Application Extension Platform running firmware version 1.2.2.8, 1.3.1.7, or 1.0.3.55 respectively, and the web management interface is accessible to potential attackers.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since no vendor patches exist, organizations should restrict web management interface access to trusted networks only, enforce strong administrator credentials, monitor for suspicious activity, and plan for replacement of affected devices.

Fix this in Rv110w Firmware Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1215 — 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-2021-1215 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