CVE-2023-2377: Ubiquiti EdgeRouter X Web Management command injection
A vulnerability was detected in Ubiquiti EdgeRouter X up to 2.0.9-hotfix.6. The impacted element is an unknown function of the component Web Management Interface. The manipulation of the argument Name results in command injection. The attack can be launched remotely. The exploit is now public and may be used. There is ongoing doubt regarding the real existence of this vulnerability. The vendor position is that post-authentication issues are not accepted as vulnerabilities.
Security readout for executives and security teams
Plain-English summary
This is a reported command-injection issue in the Ubiquiti EdgeRouter X web management interface. An authenticated user with high privileges may be able to manipulate a Name field to run commands. Public exploit material is reported, but the source bundle also notes doubt about the vulnerability’s existence and the vendor’s rejection of post-authentication issues.
Executive priority
Treat this as a high-priority exposure review, not confirmed emergency exploitation. Focus first on any EdgeRouter X devices with remotely reachable management interfaces, then verify affected firmware and compensating controls.
Technical view
CVE-2023-2377 is mapped to CWE-74 and CWE-77 for EdgeRouter X firmware 2.0.9-hotfix.0 through 2.0.9-hotfix.6. The reported vector is network-accessible web management, low complexity, no user interaction, and high privileges required. CVSS 4.0 is 8.6. The affected function is not identified in the bundle.
Likely exposure
Exposure is most relevant where EdgeRouter X web management is reachable by administrators or remote management networks. Internet-exposed management interfaces would increase business risk, but high privileges are required according to the CVSS vector and CTI tags.
Exploitation context
The bundle says exploit material is public and may be used, but KEV status is false and no cited source confirms active exploitation. Confidence is reduced because the bundle also reports ongoing doubt about the issue’s existence and a vendor position disputing post-authentication vulnerability handling.
Researcher notes
Key gaps are material: the affected function is unknown, vendor acceptance is disputed, and the bundle flags doubt about real-world validity. Do not assert active exploitation from these sources. Validate scope defensively and avoid relying on the broken exploit reference for conclusions.
Mitigation direction
Restrict EdgeRouter X web management to trusted management networks only.
Remove any internet exposure for the administrative interface.
Review Ubiquiti guidance before assuming a fixed firmware exists.
Harden administrator access with strong authentication and least-privilege operations.
Monitor for unexpected configuration changes or administrative activity.
Validation and detection
Inventory EdgeRouter X devices and record exact firmware versions.
Identify devices running 2.0.9-hotfix.0 through 2.0.9-hotfix.6.
Confirm whether web management is reachable from untrusted networks.
Review administrative logs for unusual Name-field changes or command-like input.
Track vendor and CVE updates because source confidence is limited.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
7Timeline events
1ADP providers
8Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-74 · source CWE mapping
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.