dbcve.org
Xiaomi Router FirmwareOperating system · Mi

CVE-2023-26317

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-02
Fix available
A fix is available. Upgrade to 2023.2 or later.
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
Xiaomi routers have an external interface that can lead to command injection. The vulnerability is caused by lax filtering of responses from external interfaces. Attackers can exploit this vulnerability to gain access to the router by hijacking the ISP or upper-layer routing.

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 confidence

This is a command injection vulnerability in Xiaomi routers affecting the external network interface. The flaw stems from insufficient filtering of responses received through external interfaces, allowing attackers to inject and execute arbitrary commands on the router. Exploitation is possible through hijacking the ISP connection or compromising upstream routing infrastructure.

MitigationApply vendor-supplied firmware updates for affected Xiaomi router models when released. As an interim measure, implement network segmentation to isolate router management interfaces and monitor for unauthorized changes to ISP or upstream routing configuration.

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
Xiaomi Router FirmwareOperating system
Affected:< 2023.2

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 router firmware version
    Access the router web administration panel (typically at 192.168.31.1 or 192.168.1.1) and navigate to Status or System Settings to view the current firmware version. Alternatively, use the router's command-line interface (SSH or telnet if enabled) and run: cat /proc/xiaoqiang/version or nvram get firmware_version
    Affected if The installed firmware version is lower than 2023.2 (e.g., 2022.x, older stable releases)
  2. Confirm external WAN interface is active
    Check router status page or network settings to verify the WAN (Wide Area Network) port is connected and obtaining an IP address from the ISP. The vulnerability exists on the external network interface, so this must be present.
    Affected if The router has an active WAN connection receiving external network traffic from an ISP or upstream provider
  3. Verify if remote administration is accessible from WAN
    Check router settings under Advanced Settings > Remote Management or Security Settings to see if web-based administration is accessible from the WAN side. Look for options like 'Allow remote management' or 'Remote access from WAN'
    Affected if Remote management or administration access is enabled and reachable from the external/WAN interface, making the vulnerable code path directly reachable
  4. Inspect WAN-side filtering configuration
    Examine the router's firewall or security settings to determine if any filtering or input validation is applied specifically to responses received through the WAN interface. Check for any custom firewall rules or ISP gateway configurations.
    Affected if There is no filtering or insufficient validation on responses received through the external interface

The router is affected if it runs firmware version before 2023.2 AND has an active WAN connection, particularly if remote WAN management is accessible.

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.

From vendor data
Upgrade available Upgrade to 2023.2 or later
Fixed in 2023.2
Interim mitigation

Apply vendor-supplied firmware updates for affected Xiaomi router models when released. As an interim measure, implement network segmentation to isolate router management interfaces and monitor for unauthorized changes to ISP or upstream routing configuration.

Fix this in Xiaomi Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26317 — 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-2023-26317 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