dbcve.org
Tew 713re FirmwareOperating system · Trendnet

CVE-2025-15471

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 detected in TRENDnet TEW-713RE 1.02. The impacted element is an unknown function of the file /goformX/formFSrvX. The manipulation of the argument SZCMD results in os command injection. It is possible to launch the attack remotely. The exploit is now public and may be used. The vendor confirms: "The product in question TEW-731RE for CVE-2025-15471 has been discontinued and end of life since October 23, 2020. We no longer provide support for this product, so we are not able to confirm the vulnerabilities. We will make an announcement on the website 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.

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-713RE firmware 1.02 allows remote attackers to execute arbitrary commands via the SZCMD parameter in the /goformX/formFSrvX web interface handler. The lack of input sanitization on this parameter enables complete system compromise.

MitigationSince the product is discontinued with no vendor support or patches available, immediate mitigation requires device replacement with a supported model and/or network isolation to prevent external exploitation.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tew 713re FirmwareOperating system
Affected:= 1.0.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 device model
    Access the device web interface or check device label/metadata. The vulnerable device is TRENDnet TEW-713RE.
    Affected if Device model is TRENDnet TEW-713RE
  2. Check firmware version
    Log into the device web interface and navigate to System or Status section to view firmware version, or use grep command on firmware binary if extracted: strings firmware.bin | grep '1.0.2'
    Affected if Firmware version equals 1.0.2
  3. Verify web interface is enabled
    Check if the device web interface (port 80/443) is accessible on the network. This vulnerability is exploitable through the web interface handler at /goformX/formFSrvX.
    Affected if Web interface is exposed and accessible on the network

User is affected if they have a TRENDnet TEW-713RE device running firmware version 1.0.2 with the web interface accessible on the network.

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 discontinued with no vendor support or patches available, immediate mitigation requires device replacement with a supported model and/or network isolation to prevent external exploitation.

Recommended fix High confidence
  1. This vulnerability has no remediation. TRENDnet TEW-713RE (firmware 1.0.2) is end-of-life and was discontinued on October 23, 2020.
  2. The vendor has explicitly stated they will not provide patches or support for this product.
  3. Isolate the affected device on a restricted network segment to limit exposure.
  4. Replace the end-of-life device with a currently supported model from TRENDnet or another vendor.
  5. If the device cannot be replaced immediately, consider implementing strict network access controls such as firewall rules that block all unauthorized access to the device's management interface.

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

Fix this in Tew 713re Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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