Cyber Resilience

CVE-2026-5184

Command Injection in Trendnet Tew-713Re Firmware 1.02

Published
31 March 2026
Modified
30 April 2026
CVSS Score v4 2.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.069 94th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-5184 is a low-severity Injection (CWE-74) vulnerability in Trendnet Tew-713Re Firmware. Its CVSS base score is 2.1 (Low).

Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A command injection vulnerability exists in the TRENDnet TEW-713RE wireless range extender up to firmware version 1.02. The flaw resides in an unspecified function within the /goform/setSysAdm endpoint, where unsanitized input supplied to the admuser argument is passed to a system command. The issue is tracked under CWE-74 and CWE-77 and carries a CVSS 4.0 score of 2.1.

An authenticated remote attacker can supply a crafted admuser value to execute arbitrary operating-system commands on the device. Because the attack requires only low privileges and no user interaction, an adversary who has obtained valid credentials or who can reach the web interface can achieve limited control over confidentiality, integrity, and availability of the affected extender. A publicly available proof-of-concept exploit has been posted on GitHub.

No vendor advisory, patch, or mitigation guidance has been issued; TRENDnet was notified prior to disclosure but did not respond. The public references consist solely of the exploit description and Vuldb entries.

EPSS for the CVE rose from a low baseline to a peak of 0.0141 on 2026-04-06 before receding, indicating measurable exploitation interest shortly after publication.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A vulnerability was identified in TRENDnet TEW-713RE up to 1.02. The impacted element is an unknown function of the file /goform/setSysAdm. The manipulation of the argument admuser leads to command injection. The attack can be initiated remotely. The exploit is…

more

publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-5183Same product: Trendnet Tew-713Re
CVE-2025-15471Same product: Trendnet Tew-713Re
CVE-2025-15137Same vendor: Trendnet
CVE-2026-10061Same vendor: Trendnet
CVE-2025-15136Same vendor: Trendnet
CVE-2026-10060Same vendor: Trendnet
CVE-2025-15139Same vendor: Trendnet
CVE-2023-0640Same vendor: Trendnet
CVE-2024-22545Same vendor: Trendnet
CVE-2024-37642Same vendor: Trendnet

Affected Assets

trendnet
tew-713re firmware
1.02

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

Secure engineering principles include proper neutralization and safe command construction practices.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data can detect anomalous command execution resulting from injection.

ID.RA-01 partial match
prevents

Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

prevents

Application security requirements explicitly call for controls against injection attacks in software design.

References