CVE-2020-28899
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 Web CGI Script on ZyXEL LTE4506-M606 V1.00(ABDO.2)C0 devices does not require authentication, which allows remote unauthenticated attackers (via crafted JSON action data to /cgi-bin/gui.cgi) to use all features provided by the router. Examples: change the router password, retrieve the Wi-Fi passphrase, send an SMS message, or modify the IP forwarding to access the internal network.
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 confidenceThe Web CGI script on ZyXEL LTE4506-M606 V1.00(ABDO.2)C0 devices has an authentication bypass vulnerability. The /cgi-bin/gui.cgi endpoint accepts crafted JSON action data without requiring any authentication, allowing remote attackers to access all administrative features of the router including password changes, Wi-Fi credential retrieval, SMS sending, and IP forwarding modifications.
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< v1.00\(abdo.6\)c0< v1.00\(abfr.5\)c0< v1.00\(abbc.11\)c0CVSS 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
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 model and firmware versionAccess the router's web interface or check the administrative panel for the exact model number and firmware version informationAffected if The device model is LTE4506-M606, LTE7460-M608, or Wah7706 and the firmware version is below v1.00(abdo.6)c0, v1.00(abfr.5)c0, or v1.00(abbc.11)c0 respectively
-
Verify if the CGI endpoint is internet-accessibleCheck router firewall settings or network configuration to determine if the /cgi-bin/gui.cgi endpoint is exposed to untrusted networksAffected if The CGI script is reachable from untrusted networks without VPN or ACL restrictions
-
Test the vulnerability with a benign requestSend an unauthenticated HTTP POST request to /cgi-bin/gui.cgi with crafted JSON action data (such as a read request for system status) and observe if the device responds without rejecting the requestAffected if The endpoint responds to unauthenticated requests with valid JSON data instead of requiring authentication
A user is affected if their device model matches one of the three listed models and the firmware version is below the fixed versions listed, with the CGI endpoint 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.
dbcve · scopedApply any available firmware update from ZyXEL; if no patch exists, disable remote management interfaces from internet-facing networks and place the device behind a segmented network with strict access controls.
Lte4506-M606: v1.00(abdo.6)c0 or later; Lte7460-M608: v1.00(abfr.5)c0 or later; Wah7706: v1.00(abbc.11)c0 or later
- 1. Identify the exact model number of your ZyXEL device (Lte4506-M606, Lte7460-M608, or Wah7706)
- 2. Visit the official ZyXEL support website (www.zyxel.com) and navigate to the downloads/support page for your specific model
- 3. Download the latest firmware version: For Lte4506-M606 use v1.00(abdo.6)c0 or later; For Lte7460-M608 use v1.00(abfr.5)c0 or later; For Wah7706 use v1.00(abbc.11)c0 or later
- 4. Access the router's web management interface using a wired connection
- 5. Navigate to the Administration or Maintenance section, then to the Firmware Upgrade option
- 6. Upload the downloaded firmware file and initiate the upgrade process
- 7. Wait for the router to complete the upgrade and reboot automatically
- 8. After reboot, verify the firmware version has been updated in the router's status page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28899 — 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-28899 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