CVE-2018-14558
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 · uneditedAn issue was discovered on Tenda AC7 devices with firmware through V15.03.06.44_CN(AC7), AC9 devices with firmware through V15.03.05.19(6318)_CN(AC9), and AC10 devices with firmware through V15.03.06.23_CN(AC10). A command Injection vulnerability allows attackers to execute arbitrary OS commands via a crafted goform/setUsbUnload request. This occurs because the "formsetUsbUnload" function executes a dosystemCmd function with untrusted input.
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 confidenceTenda AC7, AC9, and AC10 routers contain a command injection vulnerability in the goform/setUsbUnload handler. The formsetUsbUnload function passes unsanitized user input directly to the dosystemCmd function, allowing attackers to inject arbitrary OS commands. This is exploitable remotely without authentication due to the high CVSS score.
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.06.44_cn<= 15.03.05.19\(6318\)_cn<= 15.03.06.23_cnCVSS 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 router model and firmware versionLog into the Tenda router web management interface (usually at 192.168.0.1 or 192.168.1.1). Navigate to System Settings or Administration > Firmware/Status to view the hardware model and current firmware version.Affected if The router model is AC7, AC9, or AC10 and the firmware version is at or below 15.03.06.44_cn (AC7), 15.03.05.19(6318)_cn (AC9), or 15.03.06.23_cn (AC10).
-
Verify USB feature is enabledIn the router web interface, check USB Settings or USB Sharing settings. Look for whether USB storage support or USB function is turned on.Affected if USB support is enabled in the router configuration.
-
Confirm web interface accessibilityCheck if the router's web management interface is reachable from network segments you do not fully trust. Attempt to access the login page from an untrusted network or verify access control lists if configured.Affected if The router web interface is accessible from untrusted networks (e.g., WAN or guest networks).
-
Test for vulnerable endpoint exposureAttempt to access or curl the endpoint /goform/setUsbUnload on the router (requires authentication). For example: curl -X POST http://<router_ip>/goform/setUsbUnload -d 'any=value'. Check if the request is accepted or returns a response.Affected if The /goform/setUsbUnload endpoint responds to requests (indicating the USB functionality handler is active).
You are affected if you own a Tenda AC7, AC9, or AC10 router with firmware at or below the specified version limits, have the USB feature enabled, and the web interface is accessible 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 dataUpdate router firmware to a version beyond the listed vulnerable releases. If no patch is available, restrict administrative interface access to trusted networks or disable the USB functionality entirely.
- 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-2018-14558 — 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-2018-14558 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