Security Resilience

CVE-2023-26315

RCE in Mi Ax9000 Firmware 1.0.0 – 1.0.174

Published
26 August 2024
Modified
08 October 2024
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
EPSS Score 0.19 97th percentile
Risk Priority 73 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-26315 is a medium-severity OS Command Injection (CWE-78) vulnerability in Mi Ax9000 Firmware. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Xiaomi router AX9000 contains a post-authentication command injection vulnerability tracked as CVE-2023-26315. The flaw stems from missing input filtering and is classified under CWE-78 and CWE-77. It affects the device firmware and carries a CVSS 3.1 score of 6.5 with the vector AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H.

An attacker who has already obtained administrative credentials can supply crafted input over the network to execute arbitrary commands. Successful exploitation grants root-level access to the router, enabling full control over device configuration and traffic.

Xiaomi has published an advisory that addresses the issue at https://trust.mi.com/zh-CN/misrc/bulletins/advisory?cveId=546. The current EPSS score of 0.6750 has remained flat at its recorded peak, indicating sustained but not newly emerging exploitation interest.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

The Xiaomi router AX9000 has a post-authentication command injection vulnerability. This vulnerability is caused by the lack of input filtering, allowing an attacker to exploit it to obtain root access to the device.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
T1584.004 Server Resource Development
Adversaries may compromise third-party servers that can be used during targeting.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-26317Same vendor: Mi
CVE-2023-34214Shared CWE-77, CWE-78
CVE-2025-14204Shared CWE-77, CWE-78
CVE-2026-9515Shared CWE-77, CWE-78
CVE-2026-7202Shared CWE-77, CWE-78
CVE-2026-5690Shared CWE-77, CWE-78
CVE-2026-9384Shared CWE-77, CWE-78
CVE-2026-9532Shared CWE-77, CWE-78
CVE-2026-18900Shared CWE-77, CWE-78
CVE-2026-82690Shared CWE-77, CWE-78

Affected Assets

mi
ax9000 firmware
1.0.0 — 1.0.174

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation can discover missing or incorrect command sanitization during development.

Input validation directly neutralizes or rejects special characters that would otherwise alter OS command structure.

Least privilege reduces the permissions available to any process that could be subverted by injected commands.

Least functionality restricts available OS commands and interpreters, limiting the blast radius of injection.

Secure engineering principles require proper neutralization of untrusted input before command construction.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 mostly match
blocks

PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.

PR.PS-02 partial match
blocks

Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.

prevents

Training helps developers understand the risks of unsafe OS command construction and the need for input neutralization, but general awareness training is fallible and less directly applicable than dedicated secure coding practice (A.8.28, graded `partial` against XSS); most OS command injection instances arise from implementation mistakes that awareness alone does not prevent.

prevents

A.8.28 mandates secure coding practices (input validation, avoiding dangerous functions like system()/exec(), peer review, SAST during development) that prevent some OS command injection instances, but it is a practice-based control whose effect depends on developer skill and implementation rigor, leaving a fallible remainder that A.8.29 testing reaches more completely.

prevents

A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software CWEs like OS command injection in delivered code the way those practices do, but the effect is mediated by the supplier's implementation and is not complete.

finds

A.8.8's reach is DISCLOSURE — it finds OS command injection only where it has been published as a CVE in a third-party component, which is a minority of instances; most CWE-78 lives in first-party code that A.8.8's published-advisory and component-inventory programme does not read.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References