CVE-2020-14112
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 · uneditedInformation Leak Vulnerability exists in the Xiaomi Router AX6000. The vulnerability is caused by incorrect routing configuration. Attackers can exploit this vulnerability to download part of the files in Xiaomi Router AX6000.
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 · moderate confidenceAn information disclosure vulnerability in Xiaomi Router AX6000 allows unauthenticated remote attackers to download sensitive files from the device due to incorrect routing configuration that exposes internal file system resources to the network.
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< 1.0.56CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Confirm device model is Xiaomi Router AX6000Access router admin panel and check the device information page, or check the physical device label for model number AX6000 or Mi AX6000Affected if Device is not a Xiaomi AX6000 model - this vulnerability only applies to that specific model
-
Check installed firmware versionIn router admin panel, navigate to Settings > System Status or similar to view the current firmware version numberAffected if Firmware version is less than 1.0.56 (for example, 1.0.50, 1.0.30, etc.) - versions below 1.0.56 are affected
-
Verify router management interface network exposureCheck router firewall settings to determine if the web management interface (HTTP/HTTPS on ports 80/443) is accessible from WAN or external networks rather than LAN onlyAffected if Management interface is exposed to WAN or untrusted networks - the vulnerability allows unauthenticated remote access, so external exposure increases risk
You are affected if you have a Xiaomi AX6000 router running firmware version below 1.0.56 with its management interface accessible from outside your local network.
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 · scoped1.0.56
Apply vendor firmware update when available; until then, restrict network access to the router's management interface and disable any unnecessary exposed services.
Firmware version 1.0.56
- Access the Xiaomi Router AX6000 management interface (typically at 192.168.31.1 or miwifi.com)
- Navigate to the firmware upgrade settings (usually under Settings > Hardware Version or System Update)
- Download the official firmware version 1.0.56 or higher from Xiaomi's official support site (mi.com or trust.mi.com)
- Upload the firmware file through the router's web interface or use the Mi WiFi app for automatic update
- Wait for the upgrade process to complete - do not power off the router during this process
- After reboot, verify the firmware version has been updated to 1.0.56 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14112 — 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-14112 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