/

CVE-2026-120230

Severity:

CRITICAL RISK

(9.9)

OS Command Injection (CWE-78) in WAVLINK WN701AE Router

CVE-2026-120230

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Command Execution

Severity:

CRITICAL RISK

(9.9)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A remotely reachable function in the WAVLINK WN701AE router's ioos Web Backend may allow operating-system command injection through the vlan_name argument. If an attacker can reach and trigger the affected function, they could execute commands on the device; public exploit code has been reported.

Affected context

The reported issue affects WAVLINK WN701AE firmware version 260105, in the ioos Web Backend function del_vlan_group. The risk arises when the backend uses the vlan_name argument in operating-system command handling without adequately separating data from commands. The description identifies remote attack access but does not specify whether authentication or other deployment conditions are required.

Exploit preconditions

  • Attack surface: The ioos Web Backend function del_vlan_group, reported as remotely reachable
  • Required access: The description does not establish whether authentication is required; an attacker must be able to reach the relevant backend functionality
  • Trigger point: Processing of the vlan_name argument by the affected function
  • Why exploitation is possible: Attacker-controlled input may be interpreted as part of an operating-system command rather than treated strictly as data

Why this happens

The reported behavior is consistent with command injection: input supplied through vlan_name reaches operating-system command handling without sufficient separation or validation. This maps most directly to CWE-78: Improper Neutralization of Special Elements used in an OS Command and is also related to the broader CWE-77: Improper Neutralization of Special Elements used in a Command. The underlying insecure pattern is constructing or invoking commands using untrusted input.

Potential impact

  • An attacker may execute commands on the router.
  • Device settings or network behavior could be altered.
  • The router could be disrupted or compromised.
  • A compromised device may be used to affect connected systems or networks.

General mitigation guidance

Reduce the risk by avoiding shell command construction with untrusted values. Prefer APIs that pass arguments as separate data rather than invoking a command interpreter, and apply strict allowlists and validation to values such as VLAN names. Where command execution cannot be avoided, use safe parameterization and ensure input is never treated as executable syntax. Limit the privileges of backend processes and restrict access to management functions to trusted users and networks.

How teams detect issues like this

Review command execution paths in the Web Backend, especially uses of vlan_name and other request-derived values in del_vlan_group. Static analysis can flag shell invocation, command-string concatenation, and untrusted data flowing into process APIs. Code review should verify that inputs are strictly constrained and passed as data, while policy checks can prohibit unsafe shell usage or require approved command-execution wrappers. Monitor backend logs and device behavior for unexpected command execution or configuration changes.

Sources

SourceLink
github.comgithub.com/pipiyyb/cve/blob/main/WAVLINK_WN701AE_del_vlan_group.md
vuldb.comvuldb.com/cve/CVE-2026-120230
vuldb.comvuldb.com/submit/919242
vuldb.comvuldb.com/vuln/429589
vuldb.comvuldb.com/vuln/429589/cti

Frequently asked

questions

The report describes a remote attack path. The exact network exposure and any additional deployment requirements may vary.

The available description does not specify authentication requirements. Whether an attacker can reach the affected backend function depends on the device's access controls and configuration.

Avoid passing untrusted input through a command interpreter. Prefer direct APIs with separate arguments, and strictly validate any values that must be used.

Review data flows from backend requests to operating-system processes, use static checks for unsafe command construction, and apply least privilege to services that invoke system commands.

Find out what's already
exploitable in your codebase.