A vulnerability was identified in GL-iNet GL-MT3000 up to 4.4.5. The impacted element is the function server.set_peer of the file /cgi-bin/glc of the component wg-server.so Native Plugin. The manipulation of the argument public_key leads to command injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure and confirmed the existence of the vulnerability.
Security readout for executives and security teams
Plain-English summary
CVE-2026-18616 is a critical command-injection flaw in GL-iNet GL-MT3000 firmware versions 4.4.0 through 4.4.5. A remote attacker may abuse the WireGuard server plugin to execute system commands, potentially compromising the router’s confidentiality, integrity, and availability. Public exploit material exists, but active exploitation is not confirmed.
Executive priority
Treat this as an immediate investigation and remediation priority for affected routers, especially externally reachable devices. Successful exploitation could provide extensive control over a network-edge device. Public exploit availability increases near-term risk, although active attacks are not established. Obtain current vendor guidance and reduce interface exposure while assessing or applying remediation.
Technical view
The flaw affects server.set_peer in the wg-server.so native plugin, reached through /cgi-bin/glc. Improper handling of the public_key argument permits command injection, classified as CWE-74 and CWE-77. The supplied CVSS v2.0 score is 10.0 with network access, low complexity, and no authentication. The vendor reportedly confirmed the vulnerability.
Likely exposure
Exposure is limited to GL-iNet GL-MT3000 devices running firmware 4.4.0 through 4.4.5 where the affected WireGuard server plugin and /cgi-bin/glc interface are reachable. Internet-accessible or untrusted-network-reachable management interfaces present the greatest concern. The bundle does not establish whether default configurations expose the vulnerable path.
Exploitation context
A public proof of concept is referenced, demonstrating that exploitation knowledge is available. The source bundle says remote exploitation is possible and the exploit might be used. CVE-2026-18616 is not identified as a CISA KEV entry, and the supplied evidence does not confirm active exploitation.
Researcher notes
The evidence identifies the vulnerable function, file, parameter, affected versions, remote vector, and public proof of concept. It does not provide a vendor patch version, official workaround, default reachability analysis, or verified field exploitation. The severity uses CVSS v2.0 rather than a newer scoring version; validate organizational prioritization against deployment context.
Mitigation direction
Identify GL-MT3000 devices running firmware versions 4.4.0 through 4.4.5.
Restrict /cgi-bin/glc and router management access to trusted networks and administrators.
Disable the affected WireGuard server plugin if operationally acceptable.
Check GL-iNet guidance for patched firmware or vendor-approved remediation.
Prioritize replacement or isolation if no supported fix is available.
Validation and detection
Confirm each GL-MT3000 model and installed firmware version.
Determine whether wg-server.so and server.set_peer are present and enabled.
Verify whether /cgi-bin/glc is reachable from internet or untrusted networks.
Review relevant router and network logs for unexpected requests or command execution indicators.
After remediation, confirm the vulnerable interface is restricted or vendor-fixed firmware is installed.
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
6Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
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.