CVE-2021-1290
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 Small Business RV160, RV160W, RV260, RV260P, and RV260W VPN Routers could allow an unauthenticated, remote attacker to execute arbitrary code as the root user on an affected device. These vulnerabilities exist because HTTP requests are not properly validated. An attacker could exploit these vulnerabilities by sending a crafted HTTP request to the web-based management interface of an affected device. A successful exploit could allow the attacker to remotely execute arbitrary code on the device.
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 confidenceMultiple vulnerabilities in the web-based management interface of Cisco RV160/RV260 series VPN routers allow unauthenticated remote attackers to execute arbitrary code as root user via crafted HTTP requests that are not properly validated.
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< 1.0.01.02< 1.0.01.02< 1.0.01.02< 1.0.01.02< 1.0.01.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelCheck the physical device label or access the admin interface to confirm the exact model number (RV160, RV160w, RV260, RV260p, or RV260w)Affected if The model is any of RV160, RV160w, RV260, RV260p, or RV260w series routers
-
Check the firmware versionLog into the router web management interface and navigate to Administration > Firmware Upgrade or check the status/dashboard page for the current firmware version. Alternatively, use the CLI command 'show version' if SSH access is available.Affected if The installed firmware version is earlier than 1.0.01.02 (any version below this threshold)
-
Verify the web management interface is accessibleAttempt to access the device's web interface via HTTP/HTTPS from a browser at the device's LAN or WAN IP address. Confirm the management login page loads.Affected if The web-based management interface is reachable on any network interface (LAN or WAN)
-
Check if web management is enabled on WANIn the router web interface, go to Administration > Management > HTTP/HTTPS settings and verify whether WAN access is permitted for the management interface.Affected if Web-based management is enabled and accessible from the WAN interface
You are affected if you own an RV160 or RV260 series router running firmware below version 1.0.01.02 and the web management interface is accessible (especially from WAN).
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.
dbcve · scoped1.0.01.02
Apply Cisco firmware updates when available; if no patch exists, restrict web management interface access to trusted management networks or disable it entirely if not required.
Firmware version 1.0.01.02 or later for RV160, RV160W, RV260, RV260P, and RV260W VPN Routers
- Download the latest firmware version 1.0.01.02 or later for your specific router model from Cisco's official support site
- Access the router's web-based management interface using an administrative account
- Navigate to the Administration section and locate the Firmware Upgrade or Software Update option
- Upload the downloaded firmware file and apply the update
- Allow the device to reboot and complete the installation process
- Verify the firmware version has been updated successfully after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1290 — 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-2021-1290 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