dbcve.org
Zxv10 W908 FirmwareOperating system · Zte

CVE-2020-6880

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A ZXELINK wireless controller has a SQL injection vulnerability. A remote attacker does not need to log in. By sending malicious SQL statements, because the device does not properly filter parameters, successful use can obtain management rights. This affects: ZXV10 W908 all versions before MIPS_A_1022IPV6R3T6P7Y20.

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 confidence

An unauthenticated SQL injection vulnerability exists in ZXELINK ZXV10 W908 wireless controller devices. By sending malicious SQL statements via unsanitized parameters, remote attackers can execute arbitrary database commands without credentials and gain full management privileges.

MitigationUpdate to firmware version MIPS_A_1022IPV6R3T6P7Y20 or later. If patching is not immediately feasible, restrict network access to the device's management interface to reduce exposure.

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
Zxv10 W908 FirmwareOperating system
Affected:< mips_a_1022ipv6r3t6p7y20

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device's web management interface or check the device label to confirm the model is ZTE ZXV10 W908
    Affected if The device is not a ZTE ZXV10 W908 model, then this CVE does not apply
  2. Determine the current firmware version
    Log into the device's web interface and navigate to the status or system information page to find the firmware version, or use the command line and run 'cat /proc/version' or check the banner if accessible via telnet/SSH
    Affected if Unable to retrieve the firmware version, further investigation may be needed through other means
  3. Compare firmware version against the affected range
    Check if the installed firmware version string is lexicographically less than 'mips_a_1022ipv6r3t6p7y20'
    Affected if The firmware version is earlier than mips_a_1022ipv6r3t6p7y20, the device is vulnerable to unauthenticated SQL injection through unsanitized parameters
  4. Verify management interface accessibility
    Check if the device's HTTP/HTTPS management port is exposed to untrusted networks by reviewing firewall rules or network access control lists
    Affected if The management interface is reachable from untrusted networks and the firmware version is vulnerable, the SQL injection can be exploited remotely

A user is affected if they have a ZTE ZXV10 W908 device running firmware version earlier than mips_a_1022ipv6r3t6p7y20 with its management interface accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to firmware version MIPS_A_1022IPV6R3T6P7Y20 or later. If patching is not immediately feasible, restrict network access to the device's management interface to reduce exposure.

Recommended fix High confidence

MIPS_A_1022IPV6R3T6P7Y20

  1. Obtain the official firmware version MIPS_A_1022IPV6R3T6P7Y20 from the vendor's official support site (www.zxelink.com.cn)
  2. Verify the firmware integrity using checksums provided by the vendor
  3. Access the ZXV10 W908 device web management interface or console
  4. Navigate to the firmware upgrade section in the administrative panel
  5. Upload and apply the MIPS_A_1022IPV6R3T6P7Y20 firmware file
  6. Allow the device to complete the upgrade process and reboot
  7. After reboot, verify the firmware version has been successfully updated
  8. Confirm the SQL injection vulnerability is resolved by testing that malicious SQL input is properly sanitized
Caveat Firmware upgrades may temporarily disrupt wireless services; plan for maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zxv10 W908 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6880 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-6880 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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