dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10182

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 was determined in TRENDnet TEW-432BRP 3.10B20. The impacted element is the function formWlanSetup of the file /goform/formWlanSetup. Executing a manipulation of the argument enrollee can lead to command injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. 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

A command injection vulnerability exists in the TRENDnet TEW-432BRP router's web interface. The formWlanSetup function in /goform/formWlanSetup fails to properly sanitize the 'enrollee' parameter, allowing remote attackers to inject arbitrary OS commands via the HTTP POST request. This is a pre-authentication command injection exploitable remotely.

MitigationSince the device is End-of-Life with no vendor patch available, recommended mitigations include replacing the device with a supported model, network isolation to restrict access to trusted users only, and disabling the wireless management interface if possible.

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
    Log into the router web interface or check the device label to confirm the model is TRENDnet TEW-432BRP
    Affected if The device is not a TRENDnet TEW-432BRP router
  2. Check the firmware version
    Access the router admin panel, typically at 192.168.10.1, and navigate to the Status or System section to view the firmware version
    Affected if The firmware version is 3.10B20
  3. Verify the web interface is accessible
    Attempt to access the router web interface over HTTP or HTTPS on the LAN or WAN IP address
    Affected if The /goform/formWlanSetup endpoint is reachable
  4. Confirm remote web management is enabled
    In the router admin panel, check the Remote Management or Web Management settings to see if remote access is enabled
    Affected if Remote web management is enabled and the interface is exposed to untrusted networks
  5. Check if the WlanSetup form is present
    Inspect the router web interface HTML source or attempt to access /goform/formWlanSetup to confirm the vulnerable endpoint exists
    Affected if The formWlanSetup function with the enrollee parameter is present and accepts user input

A user is affected if they are running TRENDnet TEW-432BRP firmware version 3.10B20 with the web interface accessible and the formWlanSetup function available.

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

Since the device is End-of-Life with no vendor patch available, recommended mitigations include replacing the device with a supported model, network isolation to restrict access to trusted users only, and disabling the wireless management interface if possible.

Recommended fix High confidence
  1. This is an End-of-Life (EOL) device from 2009 with no vendor support or patches available.
  2. Replace the TRENDnet TEW-432BRP with a currently supported router from TRENDnet or another vendor.
  3. If immediate replacement is not possible, isolate the device on a dedicated network segment VLAN with strict firewall rules limiting access to only essential services.
  4. Disable remote administration (web interface) access from the internet via router/firewall rules.
  5. Monitor network traffic for any suspicious activity targeting this device.
Caveat No upgrade path available - device is EOL since 2009 with no vendor support

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10182 — 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-10182 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