Skip to main content

Tew 657Brm EUVDEUVD-2026-18406

| CVE-2026-5352 LOW
OS Command Injection (CWE-78)
2026-04-02 VulDB
2.1
CVSS 4.0 · Vendor: VulDB
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

While the CVSS 3.1 vector assigns a score of 6.3 (Medium severity) with network accessibility (AV:N), low attack complexity (AC:L), and low impact across confidentiality, integrity, and availability (C:L/I:L/A:L), the real-world risk is significantly diminished by multiple factors. The vulnerability requires authenticated access (PR:L per CVSS vector), meaning an attacker must first obtain valid credentials or exploit an authentication bypass. More critically, TrendNet confirmed in their advisory that this product has been discontinued and unsupported for over 14 years as of the disclosure date; no enterprise or even most consumer deployments are likely to still run this device. Exploitation is feasible-publicly available exploit code exists and CVSS includes Proof-of-Concept status (E:P)-but the addressable target population is effectively zero. This is a textbook case where CVSS-alone prioritization would be misleading; the legacy, end-of-life status renders the vulnerability largely academic. Organizations should deprioritize this CVE in favor of patched, supported products.

Exploit ScenarioDerived

An authenticated attacker with network access to the TEW-657BRM's web interface submits a crafted HTTP request to /setup.cgi with a malicious payload in the pcdb_list parameter containing shell metacharacters (e.g., backticks or pipe operators). The /setup.cgi script's Edit function concatenates this unsanitized input into an OS command and executes it via a shell, allowing the attacker to run arbitrary commands with the privileges of the web server process (likely root). A publicly available proof-of-concept (referenced on GitHub at https://github.com/panda666-888/vuls/blob/main/trendnet/tew-657brm/edit.md) demonstrates the exact injection technique, though practical exploitation is limited to the vanishingly small population still operating this 2011-era hardware.

Monitor Track and reassess. Why: Vendor states no customer action required.
No patch listed yet 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 02, 2026

Remote code execution via OS command injection in TrendNet TEW-657BRM 1.00.1 allows authenticated attackers to execute arbitrary commands through the pcdb_list parameter in /setup.cgi. The affected device has been end-of-life since June 2011 with no vendor support; publicly available exploit code exists but real-world impact is limited to legacy, unsupported hardware.

RemediationAI

No vendor patch is available; TrendNet explicitly stated the product is discontinued and end-of-life with no support provided. Organizations still operating this device should immediately retire and replace it with a modern, supported wireless router or network security appliance. If immediate replacement is not feasible, restrict web management access (/setup.cgi) to trusted internal IP addresses only via firewall rules, disable remote access to the device's web interface, and ensure strong, unique credentials are set if local access is required. Consult TrendNet's product support page (referenced in their advisory) for migration guidance. For reference, see VulDB entry https://vuldb.com/vuln/354705.

Affected VersionsENISA

TEW-657BRM 1.00.1

Affected Packages

euvd tew_657brm no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the /setup.cgi web interface of the TEW-657BRM wireless router, specifically in the 'Edit' function's handling of the pcdb_list argument. The underlying issue is CWE-78 (Improper Neutralization of Special Elements used in an OS Command), indicating that user-supplied input is passed unsanitized to operating system command execution routines. The CPE cpe:2.3:a:trendnet:tew-657brm identifies all versions of this specific device model; the documented affected version is 1.00.1. The attack leverages the router's web management interface, which presumably accepts configuration parameters and executes them within a shell context without proper input validation or escaping.

Know when Tew 657Brm gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 LOW
CVSS: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

Primary rating from Vendor (VulDB) · only source for this CVE.

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

4
Severity Changed
Apr 29, 2026 - 01:11 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:11 NVD
5.3 (MEDIUM) 2.1 (LOW)
PoC Detected
Apr 07, 2026 - 17:21 vuln.today
Public exploit code
CVE Published
Apr 02, 2026 - 16:00 nvd
MEDIUM 5.3

DescriptionCVE.org

A security vulnerability has been detected in Trendnet TEW-657BRM 1.00.1. This impacts the function Edit of the file /setup.cgi. Such manipulation of the argument pcdb_list leads to os command injection. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor confirms, that "[t]he product in question (...) has been discontinued and end of life since June 23, 2011, that is more than 14 years ago. We no longer provide support for this product, so we are not able to confirm the vulnerabilities. We will make an announcement on our website's product support page and notify customers who registered their products with us." This vulnerability only affects products that are no longer supported by the maintainer.

Threat Intelligence Overview

EPSS Score
0.8%
Top 25% exploitable
Exploit
POC
Public exploit code exists
Data Quality
8 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.8%
Patch available No
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

31
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy