dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10180

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in TRENDnet TEW-432BRP 3.10B20. Impacted is the function formSysCmd of the file /goform/formSysCmd. Such manipulation of the argument sysCmd leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor explains: "This product has been EOL for 15 years (since 2009). As the item has been EOL for such a long time, we are not able to replicate or fix any vulnerabilities." This vulnerability only affects products that are no longer supported by the maintainer.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TEW-432BRP router firmware contains a command injection vulnerability in the /goform/formSysCmd web handler. The sysCmd parameter passed to the formSysCmd function is not properly sanitized, allowing an attacker to inject arbitrary OS commands through the web interface. This is exploitable remotely, likely requiring network access to the router's administrative interface.

MitigationThis is an End-of-Life device with no vendor patch available. The only effective remediation is to decommission and replace the affected router with a supported model. If immediate replacement is not possible, network segmentation should be applied to restrict access to the router's administrative interface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the router's web administration interface or check the physical device label for the exact model number. Confirm it is a TRENDnet TEW-432BRP device.
    Affected if The device is a TRENDnet TEW-432BRP router.
  2. Verify firmware version
    Log into the router web interface and navigate to the Status or System Information page to view the installed firmware version. Compare it against any available firmware release notes from TRENDnet.
    Affected if A firmware version is installed on the TEW-432BRP device (no specific version range provided; all versions may be affected).
  3. Check if web management interface is accessible
    Attempt to access the router's IP address via HTTP/HTTPS from a browser. The default IP is typically 192.168.10.1. Determine whether the login page loads.
    Affected if The router web management interface is reachable from the network.
  4. Determine remote management exposure
    In the router web interface, go to the Administration or Remote Management settings section. Check if remote management (web access from WAN/outside) is enabled and note the allowed IP ranges or interfaces.
    Affected if Remote management or web interface access from WAN is enabled, allowing unauthenticated or low-privilege users to reach the login page.
  5. Locate the vulnerable endpoint
    If logged in, navigate to the System Command or SysCmd page (often under Administration or Advanced settings). Inspect whether the sysCmd parameter is present in forms or URLs.
    Affected if The formSysCmd function with the sysCmd parameter is present and accessible to authenticated users.

You are affected if you are using a TRENDnet TEW-432BRP router with its web management interface accessible (especially from remote networks) and the sysCmd command execution feature is present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

This is an End-of-Life device with no vendor patch available. The only effective remediation is to decommission and replace the affected router with a supported model. If immediate replacement is not possible, network segmentation should be applied to restrict access to the router's administrative interface.

Recommended fix High confidence
  1. Replace the affected TRENDnet TEW-432BRP router with a currently supported model from TRENDnet or another vendor, as this device is End-of-Life and no longer receives security updates
  2. If immediate replacement is not possible, place the device behind a firewall and restrict network access to trusted IP addresses only
  3. Disable remote administration interfaces if not absolutely necessary
  4. Monitor the network for any suspicious traffic targeting the /goform/formSysCmd endpoint
  5. Consider deploying an intrusion detection system (IDS) to detect potential exploitation attempts
Caveat Replacing an EOL device may require reconfiguring network settings and re-establishing port forwarding or VPN configurations

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10180 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10180 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data