CVE-2020-14119
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 · uneditedThere is command injection in the addMeshNode interface of xqnetwork.lua, which leads to command execution under administrator authority on Xiaomi router AX3600 with rom versionrom< 1.1.12
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 confidenceCommand injection vulnerability in the addMeshNode function of xqnetwork.lua on Xiaomi router AX3600 allows remote attackers to inject and execute arbitrary operating system commands with administrator privileges due to unsanitized user input being passed to system shell.
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.1.12CVSS 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 modelCheck the device label or web interface header to confirm the model is Mi AX3600 (also sold as Xiaomi AIoT Router AX3600)Affected if Model is Mi AX3600 or AX3600
-
Check firmware versionLog into the router web interface and navigate to Status or Settings > Firmware Version, or use the command line: cat /proc/xqfpga_version or nvram get firmware_versionAffected if Firmware version is below 1.1.12 (e.g., 1.0.x, 1.1.x versions prior to 1.1.12)
-
Verify web management interface accessibilityAttempt to access the router admin interface at http://192.168.31.1 or the configured LAN IP address from a browserAffected if Web interface is reachable from untrusted networks (the attack vector requires network access to the admin panel)
-
Check mesh node configuration accessLocate the Mesh or Network settings in the web interface where addMeshNode function would be invoked, or inspect network requests to /cgi-bin/luci/ endpoints related to mesh configurationAffected if Mesh configuration features are accessible without additional authentication barriers beyond admin login
You are affected if you own a Xiaomi AX3600 router with firmware version below 1.1.12 and the router web management 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.
dbcve · scoped1.1.12
Upgrade Xiaomi AX3600 router firmware to version 1.1.12 or later to patch the command injection vulnerability; until then, restrict administrative interface access to trusted networks only.
Firmware version 1.1.12
- Navigate to the Xiaomi router AX3600 admin interface (typically at 192.168.31.1)
- Locate the firmware update or system settings section
- Download firmware version 1.1.12 or later from Xiaomi's official support site (trust.mi.com or official firmware downloads)
- Upload the firmware file and apply the update
- Verify the router is running firmware version 1.1.12 or later after reboot
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14119 — 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-14119 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