/

CVE-2026-11556

Severity:

HIGH RISK

(8.8)

OS Command Injection (CWE-78) in Tenda F451 Router

CVE-2026-11556

Deferred

Vulnerability type

Category:

OS Command Injection

CWE:

CWE-77, CWE-78

Impact:

Remote Code Execution on Network Device

Severity:

HIGH RISK

(8.8)

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

Tenda F451 routers contain an OS command injection flaw in the Web Management Interface, specifically in the formWriteFacMac handler for the /goform/WriteFacMac endpoint.

By manipulating the mac parameter, a remote attacker can inject system commands that run with the router's web process privileges, making exposed devices at risk of full compromise.

Affected context

The vulnerability occurs in the web-based administration interface of Tenda F451 firmware versions 1.0.0.7 and 1.0.0.9.

It affects deployments where the management interface is reachable over the network, either from the local LAN or, in less secure setups, from the internet.

The flaw resides in the /goform/WriteFacMac endpoint, which processes the mac parameter without sufficient command-line sanitization before invoking underlying system utilities.

Exploit preconditions

  • Attack surface: HTTP-based Web Management Interface on the Tenda F451 router
  • Required access: Network reachability to the admin interface; authentication requirements depend on specific device configuration
  • Trigger point: Sending crafted requests to /goform/WriteFacMac that control the mac argument
  • Why exploitation is possible: User-supplied input is concatenated into shell commands or passed to a command interpreter without robust validation or escaping, enabling injection of additional OS commands

Why this happens

The root cause aligns with CWE-78: Improper Neutralization of Special Elements used in an OS Command.

The formWriteFacMac function accepts a MAC address value and appears to pass it directly to an underlying shell command or system call, relying on the command interpreter to process the input.

Because the implementation does not correctly filter or escape shell metacharacters, attackers can break out of the intended command context and append arbitrary commands.

This pattern reflects a broader command injection bug class where application-layer parameters are treated as trusted command fragments rather than strictly validated data.

Potential impact

  • Remote execution of arbitrary system commands on the router
  • Complete takeover of the device's management plane
  • Interception, modification, or redirection of network traffic
  • Installation of persistent malware or participation in botnets
  • Use of the compromised router as a pivot point for attacks on internal network hosts

General mitigation guidance

Mitigation usually focuses on eliminating direct shell invocation with user-controlled parameters and hardening input handling:

  • Prefer APIs that invoke system functionality without passing through a shell, using parameterized system calls where available
  • Apply strict input validation and canonicalization for fields like MAC addresses, enforcing fixed formats and rejecting unexpected characters outright
  • Avoid concatenating user-supplied strings into command lines; if commands are unavoidable, constrain inputs to whitelisted character sets and pre-defined options
  • Run the web management service with the least privileges necessary, reducing the blast radius if command injection occurs
  • Limit exposure of the web management interface to trusted networks and disable WAN-side administration by default

How teams detect issues like this

Effective detection combines code-centric and runtime approaches:

  • Static analysis: Scan firmware or source code for patterns where request parameters are passed to system, popen, or shell invocation wrappers without strict validation
  • Code review: Flag any use of shell commands in the web interface, particularly around configuration endpoints; verify that inputs are validated against rigid schemas (e.g., MAC address formats)
  • Policy enforcement: Establish secure coding guidelines banning shell concatenation with user input and require security sign-off for any system-level calls in web handlers
  • Runtime monitoring: Use network intrusion detection systems to look for anomalous requests containing shell metacharacters targeting /goform/WriteFacMac or similar endpoints

Sources

SourceLink
github.comgithub.com/Robots10/IoT_vlu/blob/main/reports/Tenda/formWriteFacMac2/formWriteFacMac.md
vuldb.comvuldb.com/cve/CVE-2026-11556
vuldb.comvuldb.com/submit/836476
vuldb.comvuldb.com/vuln/369166
vuldb.comvuldb.com/vuln/369166/cti
tenda.com.cntenda.com.cn/

Frequently asked

questions

It can be, if the router's web management interface is exposed to the internet or reachable through port forwarding or misconfiguration. Otherwise, exploitation is typically limited to attackers on the local network.

That depends on the router's configuration. On some setups, authentication may be required to reach the vulnerable endpoint, while on less secure configurations, the endpoint may be accessible without proper authentication.

Remove direct shell command usage where user data is involved, rely on high-level APIs instead, and enforce strict format validation on all configuration parameters before processing them.

Adopt secure coding practices that prohibit passing user-controllable data to command interpreters, enforce rigorous validation and whitelisting for all request parameters, and include automated security testing and code review focused on injection risks throughout the development lifecycle.

Find out what's already
exploitable in your codebase.