CVE Intelligence
CISA KEV Critical Injection exploit reference

CVE-2018-14558 — Tenda AC7, AC9, and AC10 Routers Command Injection Vulnerability

An 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.

Published Oct 30, 2018 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, GitHub Security Advisories, CVE Program (cve.org) e CISA ADP · CNA: mitre

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Nov 3, 2021
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 8.5% (30-day exploitation probability)+14
  • Technical severity (critical)+10
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Nov 3, 2021
EPSS FIRST
8.51%
ahead of 95% of scored CVEs · Oct 14, 2026
Affects
Tenda
Ac10 Firmware and 2 more
CVSS base
9.8
Critical · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

Apply updates per vendor instructions.

US federal deadline: May 3, 2022 — passed 1626 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Tenda Ac10 Firmware, Tenda Ac7 Firmware, Tenda Ac9 Firmware).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 95% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Tenda Ac10 Firmware ≤ 15.03.06.23_cn Vulnerable NIST National Vulnerability Database
Tenda Ac7 Firmware ≤ 15.03.06.44_cn Vulnerable NIST National Vulnerability Database
Tenda Ac9 Firmware ≤ 15.03.05.19\(6318\)_cn Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
9.8 CVSS 3.1 Critical — — CISA-ADP via CVE Program (cve.org) e CISA ADP
9.8 CVSS 3.0 Critical — — GitHub, Inc. via GitHub Security Advisories
10.0 CVSS 2.0 High 10.0 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Nov 3, 2021
Federal deadline
May 3, 2022
passed 1626 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 8.51%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
  • Hunt retroactively in logs from before Nov 3, 2021 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPSapplication logsendpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · tenda/ac7 firmware, tenda/ac9 firmware, tenda/ac10 firmware
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2021
  • Added to CISA KEV catalog
    Nov 2, 2021 · CISA
  • 2018
  • CVE published
    Oct 30, 2018 · mitre

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Tenda
every CVE for this vendor
2021-11
what else CISA listed that month
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-51846 Tenda AC7 Firmware Stack Buffer Overflow in wanSpeed Parameter (CVE-2026-51846) Jun 19, 2026
  • CVE-2026-51843 Tenda AC7 firmware stack buffer overflow in wanMTU handler Jun 19, 2026
  • CVE-2026-51844 Tenda AC7 Stack Buffer Overflow in AdvSetMacMtuWan via cloneType Jun 19, 2026
  • CVE-2026-51845 Tenda AC7 Stack-based Buffer Overflow in AdvSetMacMtuWan Interface Jun 19, 2026
  • CVE-2026-6015 Tenda AC9 POST Request QuickIndex formQuickIndex stack-based overflow Apr 10, 2026
  • CVE-2026-6016 Tenda AC9 POST Request WizardHandle decodePwd stack-based overflow Apr 10, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2018-14558 is "Tenda AC7, AC9, and AC10 Routers Command Injection Vulnerability", rated Critical. It affects Ac10 Firmware (Tenda); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 8.51% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.