dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-15485

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-12
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 5 weeks old

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 flaw has been found in TRENDnet TEW-821DAP 1.11B03. The impacted element is the function sub_43F2C4 of the file /goform/tools_nslookup of the component DNS Lookup Handler. This manipulation of the argument nslookup_target/dns_server causes os command injection. The attack can be initiated remotely. The vendor explains: "We are unable to confirm the existence of the vulnerabilities for (...) TEW-821DAP (v1.0R) as these items have been EOL. " 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

OS command injection vulnerability in TRENDnet TEW-821DAP 1.11B03's DNS Lookup Handler (function sub_43F2C4 in /goform/tools_nslookup). The nslookup_target and dns_server parameters are not properly sanitized before being passed to system commands, allowing remote attackers to execute arbitrary OS commands via crafted input.

MitigationSince the product is End-of-Life with no vendor patch available, the primary mitigation is to remove the device from production or isolate it behind network segmentation with strict firewall rules that block all access to the management 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. Confirm device model is TRENDnet TEW-821DAP
    Access the device web management interface or physically inspect the device label to verify the exact model number
    Affected if Device model is not TEW-821DAP
  2. Check firmware version is 1.11B03
    In the web interface, navigate to the Status or Firmware Upgrade page to view the installed firmware version
    Affected if Firmware version is 1.11B03 and matches the affected release
  3. Verify web management interface is accessible
    Attempt to reach the device IP via HTTP/HTTPS from the network
    Affected if Web interface is reachable and responds to requests
  4. Confirm DNS Lookup function is available
    Locate the tools_nslookup or DNS Lookup feature in the web interface, typically under System Tools or Network Utilities
    Affected if DNS Lookup function is present and enabled

Device is affected if it is a TRENDnet TEW-821DAP running firmware version 1.11B03 with an accessible web management interface where the DNS Lookup 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

Since the product is End-of-Life with no vendor patch available, the primary mitigation is to remove the device from production or isolate it behind network segmentation with strict firewall rules that block all access to the management interface.

Recommended fix High confidence
  1. This vulnerability affects TRENDnet TEW-821DAP firmware 1.11B03 which is End-of-Life (EOL) and no longer supported by the vendor.
  2. The vendor (TRENDnet) has explicitly stated they cannot confirm this vulnerability as the product is EOL.
  3. No official firmware patch or fix will be released by the vendor for this product.
  4. Replace the EOL device with a currently supported model from TRENDnet or another vendor.
  5. If immediate replacement is not possible, restrict network access to the device's management interface by placing it behind a firewall or in a VLAN with limited access.
  6. Disable the DNS lookup functionality if not needed, or restrict access to trusted IP addresses only.
  7. Monitor the network for any suspicious activity targeting the affected device.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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