dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-15487

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 vulnerability was found in TRENDnet TEW-821DAP 1.11B03. This impacts the function sub_41FBD0 of the file /goform/system_ntp of the component Firmware Update Handler. Performing a manipulation of the argument Hostname results in os command injection. The attack may 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 firmware where the Hostname parameter in the /goform/system_ntp endpoint (function sub_41FBD0) is not properly sanitized before being passed to OS command execution, allowing remote attackers to execute arbitrary commands.

MitigationSince the product is End-of-Life with no available patch, the device should be decommissioned or replaced with a supported model. If continued use is required, implement strict network isolation and firewall rules to limit exposure to this vulnerability.

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
    Inspect the device label on the hardware or log into the web admin interface and check the status or system information page for the exact model name
    Affected if The device model is not TRENDnet TEW-821DAP
  2. Determine the installed firmware version
    Log into the web admin interface and navigate to System or Administration > Firmware Upgrade to view the current firmware version, or check the device label for a firmware version sticker
    Affected if The firmware version cannot be determined or is an unpatched release of this model
  3. Verify the web management interface is accessible from the network
    Attempt to reach the device's IP address on HTTP/HTTPS ports (typically 80/443) from the network perspective you are auditing
    Affected if The web interface is reachable over the network and accepts authentication requests
  4. Confirm the NTP configuration endpoint exists
    Access the URL /goform/system_ntp on the device's web interface (may require login) and verify the page loads with Hostname or NTP Server input fields
    Affected if The /goform/system_ntp endpoint exists and accepts a Hostname parameter for NTP server configuration

The device is affected if it is a TRENDnet TEW-821DAP with an accessible web interface where the NTP Hostname parameter at /goform/system_ntp can be manipulated without proper sanitization, allowing potential remote command injection.

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 available patch, the device should be decommissioned or replaced with a supported model. If continued use is required, implement strict network isolation and firewall rules to limit exposure to this vulnerability.

Recommended fix Low confidence
  1. This vulnerability affects TRENDnet TEW-821DAP firmware version 1.11B03 which has reached End of Life (EOL) and is no longer supported by the vendor.
  2. The vendor (TRENDnet) has explicitly stated they cannot confirm the existence of vulnerabilities for this EOL product.
  3. No patched firmware version or vendor patch is available for this legacy device.
  4. Recommendation: Replace the EOL device with a currently supported model from TRENDnet or another vendor.
  5. If the device must remain in service, consider network isolation and restrict administrative access to trusted internal networks only.
Caveat The device is End of Life with no vendor support or patches available; replacement is the only recommended mitigation.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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