dbcve.org
Rv215w FirmwareOperating system · Cisco

CVE-2022-20876

HIGH · 7.2 CVSS v3.1 Published 2022-07-21
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 on an affected device or cause the device to restart unexpectedly, resulting in a denial of service (DoS) condition. These vulnerabilities are due to insufficient validation of user fields within incoming HTTP packets. An attacker could exploit these vulnerabilities by sending a crafted request to the web-based management interface. A successful exploit could allow the attacker to execute arbitrary commands on an affected device with root-level privileges or to cause the device to restart unexpectedly, resulting in a 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

Multiple command injection vulnerabilities in the web-based management interface of Cisco Small Business RV series routers (RV110W, RV130, RV130W, RV215W) allow authenticated remote attackers with Administrator credentials to execute arbitrary commands with root-level privileges via insufficiently validated user fields in HTTP packets. A separate DoS vulnerability can also cause unexpected device restarts.

MitigationSince Cisco has not released patches (device is likely end-of-life), implement network segmentation to restrict management interface access to trusted networks/VPN only, or replace affected routers with supported models. Monitor for suspicious administrative activity.

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
Rv215w FirmwareOperating system
Affected:= 1.0.3.55
Rv130w FirmwareOperating system
Affected:= 1.0.3.55
Rv130 FirmwareOperating system
Affected:= 1.0.3.55
Rv110w FirmwareOperating system
Affected:= 1.0.3.55
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 device model and firmware version
    Access the router's web-based management interface and navigate to Status > System Summary, or log in via CLI and run 'show version' to display the hardware model and firmware version.
    Affected if The device is a RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform running firmware version 1.0.3.55 exactly.
  2. Confirm web-based management interface is enabled
    In the web UI, go to Firewall > General or Administration > Management Interface and verify that HTTP or HTTPS management access is enabled. Check which interfaces (LAN/WAN) allow this access.
    Affected if The web-based management interface is accessible, especially if exposed to WAN.
  3. Verify Administrator account existence
    In the web UI, navigate to Administration > User Management > Users to list all accounts with Administrator privilege level.
    Affected if At least one Administrator-level account exists on the device (required for exploitation).
  4. Review system logs for suspicious commands
    In the web UI, go to Status > Logs or use CLI command 'show log' to review recent system logs. Look for unexpected or unfamiliar commands in the log history.
    Affected if Logs contain unfamiliar commands, especially shell commands, or show administrative actions not performed by authorized staff.
  5. Check for unexpected processes or configuration changes
    Use CLI 'show processes' or review running configuration via 'show running-config' for any unfamiliar processes, cron jobs, or port forwards added without authorization.
    Affected if Unexpected processes, unauthorized configuration changes, or unfamiliar cron entries are present.

The device is affected only if it is a RV110W, RV130, RV130W, RV215W, or Application Extension Platform running exactly firmware version 1.0.3.55 AND has the web management interface accessible with Administrator accounts configured.

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

Since Cisco has not released patches (device is likely end-of-life), implement network segmentation to restrict management interface access to trusted networks/VPN only, or replace affected routers with supported models. Monitor for suspicious administrative activity.

Recommended fix High confidence
  1. 1. Restrict access to the router's web-based management interface to trusted networks only by configuring ACLs on upstream devices or firewall rules.
  2. 2. Change default administrator credentials to strong, unique passwords following Cisco best practices.
  3. 3. Disable remote management access (HTTP/HTTPS) on WAN interfaces if not required, limiting access to LAN-side management only.
  4. 4. Monitor for unauthorized access attempts and review router logs regularly.
  5. 5. Consider network segmentation to isolate the router in a dedicated management VLAN with limited connectivity.

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

Fix this in Rv215w Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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