CVE-2021-1146
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 inject arbitrary commands that are executed with root privileges. 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 a targeted device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system. To exploit these vulnerabilities, an attacker would need to have valid administrator credentials on an 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 confidenceCommand injection vulnerabilities in the web-based management interface of Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers allow authenticated attackers to inject arbitrary commands via crafted HTTP requests. The vulnerabilities stem from improper validation of user-supplied input and enable execution with root privileges on the underlying operating system.
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 device modelLocate the Cisco Small Business router model number (RV110W, RV130, RV130W, or RV215W) or confirm if the device is running Cisco Application Extension Platform (AXP). This is typically found on the device label, web management interface status page, or SNMP inventory.Affected if The device is a Cisco RV110W, RV130, RV130W, RV215W router, or Cisco Application Extension Platform.
-
Check firmware versionAccess the web-based management interface and navigate to the status or system information page to view the firmware version. Alternatively, check via CLI using 'show version' or SNMP. Compare the installed version against the affected versions: 1.2.2.8 or 1.3.1.7 for routers; 1.0.3.55 for AXP.Affected if The firmware version is exactly 1.2.2.8 or 1.3.1.7 for RV-series routers, or exactly 1.0.3.55 for Application Extension Platform.
-
Verify web management interface is enabledLog into the router web interface and navigate to the administration or access settings. Confirm whether the web-based management interface (HTTP/HTTPS) is enabled. Check both the primary management access and any separate guest management features if applicable.Affected if The web-based management interface is enabled and accessible.
-
Confirm management access exposureReview the network configuration to determine if the web management interface is exposed to untrusted networks. Check firewall rules, port forwarding settings, and WAN access configuration to see if HTTP (port 80) or HTTPS (port 443) management ports are reachable from outside the trusted network.Affected if The web management interface is reachable from untrusted networks or the internet.
The environment is affected if the device is a Cisco RV110W, RV130, RV130W, RV215W router, or Application Extension Platform running firmware version 1.2.2.8, 1.3.1.7, or 1.0.3.55 respectively, and the web-based management interface is enabled and accessible (especially if exposed to untrusted networks).
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 software updates, organizations should immediately restrict web management interface access to trusted networks or IPs only, consider network segmentation, and evaluate replacement of affected devices given the critical nature of the vulnerability and lack of vendor patch.
- Consultation4.0 h
- Implementation8.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1146 — 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-1146 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