CVE-2025-15472: TRENDnet TEW-811DRU · OS Command Injection
Affects TRENDnet TEW-811DRUSource CVE Database V5
Not known to be exploited · 22% EPSS · CVSS 8.6 High.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 22.3% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 6 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TRENDnetTEW-811DRU | Affected
| Fixed in– |
AI-suggested
Given the absence of an official patch from TRENDnet, organizations should implement the following specific mitigations: 1) Immediately isolate affected TEW-811DRU devices from untrusted networks, especially the internet, to prevent remote exploitation. 2) Disable remote management interfaces or restrict access to trusted IP addresses only. 3) Monitor network traffic for unusual HTTP requests targeting the uapply.cgi endpoint or suspicious DeviceURL parameter usage. 4) Replace affected devices with alternative routers from vendors with active security support if possible. 5) If replacement is not feasible, consider deploying network-level protections such as web application firewalls (WAFs) or intrusion prevention systems (IPS) to detect and block exploitation attempts. 6) Regularly audit device firmware versions and configurations to ensure no unauthorized changes occur. 7) Maintain comprehensive network segmentation to limit lateral movement if a device is compromised. 8) Engage in active threat intelligence sharing to stay informed about emerging exploits or vendor updates. These steps go beyond generic advice by focusing on network isolation, monitoring specific attack vectors, and compensating for the lack of vendor patching.
Description
A flaw has been found in TRENDnet TEW-811DRU 1.0.2.0. This affects the function setDeviceURL of the file uapply.cgi of the component httpd . This manipulation of the argument DeviceURL causes os command injection. The attack can be initiated remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.