CVE-2020-10987
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 · uneditedThe goform/setUsbUnload endpoint of Tenda AC15 AC1900 version 15.03.05.19 allows remote attackers to execute arbitrary system commands via the deviceName POST parameter.
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 confidenceA command injection vulnerability exists in the Tenda AC15 AC1900 router firmware (version 15.03.05.19). The /goform/setUsbUnload web endpoint accepts user input via the deviceName POST parameter without proper sanitization, allowing remote attackers to inject and execute arbitrary operating system commands on the 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= 15.03.05.19CVSS 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 modelAccess the router's web interface or check the physical device label to confirm it is a Tenda AC15 AC1900 router.Affected if The device is not a Tenda AC15 model.
-
Check the firmware versionLog into the router web interface and navigate to System Settings > Firmware Upgrade or similar, or use the command: curl http://192.168.0.1/goform/getSysInfo (adjust IP as needed) to retrieve the firmware version.Affected if The firmware version is 15.03.05.19.
-
Verify the vulnerable endpoint existsSend a request to the /goform/setUsbUnload endpoint: curl -X POST http://192.168.0.1/goform/setUsbUnload -d 'deviceName=test' (adjust IP as needed). A response (even an error) indicates the endpoint is present.Affected if The endpoint responds, indicating it exists on the device.
-
Confirm USB feature is configuredCheck the router web interface for USB-related settings (USB Sharing, USB Device, etc.) under Advanced or USB settings. The vulnerable endpoint handles USB unloading, so USB must be enabled for exploitation.Affected if USB functionality is enabled or a USB device is attached.
-
Check if remote administration is accessibleVerify the router's web interface is accessible from the WAN/outside network. Check under System Settings > Remote Management, or test connectivity to port 80/443 from an external IP.Affected if Remote web management is enabled and accessible from outside the local network.
You are affected if you have a Tenda AC15 router running firmware version 15.03.05.19 with the /goform/setUsbUnload endpoint accessible and either USB or remote administration enabled.
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 vendor-supplied firmware patch if available; otherwise disable USB functionality, implement network segmentation to limit exposure, or replace the affected device with a supported model.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10987 — 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-10987 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