CVE-2026-5183
Remote Command Injection in TRENDnet TEW-713RE Routing Function
Publication date: 2026-03-31
Last updated on: 2026-04-30
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| trendnet | tew-713re_firmware | 1.0.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-77 | The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The CVE-2026-5183 vulnerability affects the Trendnet TEW-713RE router, version 1.02. It is a stack overflow and command injection vulnerability exploitable remotely via the HTTP route `/goform/addRouting`.
The vulnerability arises from improper handling of the `dest` parameter in the `sub_421494` function. Specifically, the `dest` parameter is concatenated using `strcat` into a buffer without any length checks, leading to a buffer overflow.
Subsequently, the contents of this buffer are passed to the `popen` function, enabling command injection. This means an attacker can remotely execute arbitrary commands on the device by manipulating the `dest` parameter.
- Stack Overflow PoC: Sending a POST request with an excessively long `dest` parameter causes a buffer overflow.
- Command Injection PoC: Sending a POST request with `dest=;ls > /1.txt` injects a shell command that lists directory contents and writes the output to a file.
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary commands on the affected Trendnet TEW-713RE router. This can lead to full compromise of the router device.
An attacker could manipulate the router to disrupt network operations, intercept or redirect traffic, install malicious software, or gain further access to the internal network.
Because the exploit is publicly disclosed and may be actively used, unpatched devices are at significant risk.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending specially crafted POST requests to the affected router's HTTP endpoint `/goform/addRouting` and observing the response or behavior.
- Send a POST request with an excessively long `dest` parameter (e.g., thousands of 'a' characters) to test for buffer overflow.
- Send a POST request with a command injection payload such as `dest=;ls > /1.txt` to check if arbitrary commands can be executed.
Example command using curl to test command injection: `curl -X POST -d "dest=;ls > /1.txt" http://<router-ip>/goform/addRouting`
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The CVE-2026-5183 vulnerability allows remote attackers to execute arbitrary commands on the affected Trendnet TEW-713RE router. This can lead to unauthorized access and potential compromise of the network and any data transmitted through the device.
Such a compromise could impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of personal and sensitive data. If the router is used in environments subject to these regulations, exploitation of this vulnerability could result in unauthorized data access or breaches, thereby violating regulatory requirements for data security and privacy.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2026-5183 vulnerability in the TRENDnet TEW-713RE router, immediate steps include restricting remote access to the device, especially to the HTTP route /goform/addRouting which is vulnerable to command injection.
Since the vulnerability allows remote command execution via the dest parameter, it is critical to limit network exposure by placing the device behind a firewall or disabling remote management features if possible.
Monitor the device for any unusual activity or unexpected files such as /1.txt which may indicate exploitation attempts.
Because the vendor has not responded with a patch, consider replacing the device or upgrading to a more secure model if mitigation is not feasible.