CVE-2021-1210
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 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 confidenceMultiple input validation vulnerabilities in the web-based management interface of Cisco RV110W, RV130, RV130W, and RV215W routers allow authenticated attackers to execute arbitrary code as root or cause device reload via crafted HTTP requests. The vulnerabilities stem from improper validation of user-supplied input in the management interface.
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.2.2.8= 1.3.1.7= 1.2.2.8= 1.3.1.7= 1.2.2.8= 1.3.1.7= 1.2.2.8= 1.3.1.7= 1.0.3.55CVSS 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 the router modelAccess the device web management interface or CLI and look for the model number displayed on the status or system information page. Alternatively, use the CLI command 'show version' to display the model name.Affected if The device is a Cisco RV110W, RV130, RV130W, or RV215W router, or the Cisco Application Extension Platform.
-
Check the firmware versionIn the web interface, navigate to the Status or System Summary page to view the firmware version. From CLI, use the 'show version' command which displays the firmware build number.Affected if The firmware version is exactly 1.2.2.8 or 1.3.1.7 for RV110W, RV130, RV130W, or RV215W models. For the Application Extension Platform, the version is 1.0.3.55.
-
Verify web-based management is enabledIn the web interface, go to the Administration or Management settings and check if HTTP or HTTPS management access is enabled. From CLI, check the running configuration for 'ip http server' or 'ip http secure-server' commands.Affected if HTTP (port 80) or HTTPS (port 443) management interface is accessible and enabled on the device.
-
Confirm administrative access methodReview the device configuration to determine if remote web management is accessible from WAN interfaces or limited to LAN only. Check the access control lists or firewall rules governing HTTP/HTTPS traffic.Affected if The web management interface is exposed beyond the trusted local network, allowing authenticated attackers to send crafted HTTP requests.
You are affected if you are running an exact firmware version 1.2.2.8 or 1.3.1.7 on Cisco RV110W, RV130, RV130W, or RV215W routers (or version 1.0.3.55 on the Application Extension Platform) and the web-based management interface is enabled and accessible.
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 dataSince Cisco has not released patches, organizations should restrict web management interface access to trusted networks only, enforce strong administrator credentials, monitor for suspicious HTTP activity, and consider replacing affected devices with supported models.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1210 — 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-1210 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