Rv110w FirmwareOperating system · Cisco
CVE-2020-3268
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 · uneditedMultiple vulnerabilities in the web-based management interface of Cisco RV110W, RV130, RV130W, and RV215W Series Routers could allow an authenticated, remote attacker with administrative privileges to execute arbitrary commands. For more information about these vulnerabilities, see the Details section of this advisory.
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 confidenceAuthenticated command injection vulnerability in the web-based management interface of Cisco RV110W, RV130, RV130W, and RV215W Series Routers allows an attacker with administrative privileges to execute arbitrary operating system commands on the affected device.
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
<= 1.2.2.5
Rv130 FirmwareOperating system
<= 1.0.3.54
Rv130w FirmwareOperating system
<= 1.0.3.54
Rv215w FirmwareOperating system
<= 1.3.1.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the model number on the device physical label or access the web management interface and check the status or system information page for the exact model designation (RV110W, RV130, RV130W, or RV215W)Affected if The model is one of RV110W, RV130, RV130W, or RV215W
-
Check firmware versionAccess the router web interface, navigate to the Administration, Status, or System Information page and record the firmware version number displayedAffected if The firmware version is 1.2.2.5 or lower for RV110W, 1.0.3.54 or lower for RV130/RV130W, or 1.3.1.5 or lower for RV215W
-
Verify web-based management is enabledIn the router web interface, go to the Administration or Management settings and check if the HTTP/HTTPS management interface is turned onAffected if Web-based management is enabled on the device
-
Check management interface accessibilityReview the management access settings to determine if the web interface is reachable from LAN-only or also from WAN (remote management)Affected if The management interface is accessible from WAN or untrusted networks
-
Confirm administrative access exposureDetermine whether the router admin credentials could be accessed by unauthorized users or if the management port is exposed to the internetAffected if The administrative interface is exposed to the internet or untrusted users have potential credential access
The device is affected if it is an RV110W, RV130, RV130W, or RV215W model running firmware at or below the specified version limits and its web-based management interface is accessible to the attacker.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Cisco firmware updates for the affected router models. If patches are unavailable, restrict management interface access to trusted networks only, disable remote management where possible, and monitor for unauthorized administrative access.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3268 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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