CVE Intelligence
Skip to main content
highRemote Code Execpublic exploit

CVE-2026-75984

CVE-2026-75984 — TRENDnet TEW-823DRU admin.cgi command injection

A vulnerability was detected in TRENDnet TEW-823DRU 1.1.02b01. Impacted is an unknown function of the file /cgi-bin/admin.cgi. The manipulation of the argument Hostname results in command injection. The attack can be launched remotely. The exploit is now public and may be used.

Published Updated Sources: NVD, TRENDnet (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

0%

ahead of 0% of scored CVEs

Affects

TRENDnet

TEW-823DRU

CVSS base

7.4

high · 6 sources

Remediation

The vendor's own words where we have them.

Upgrade TEW-823DRU to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Prioritize based on EPSS, PoC availability, and external exposure.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
TRENDnetTEW-823DRU1.1.02b01Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Low

Confidentiality

Low

Integrity

Low

Scope

Changed

Attack Complexity

Low

Attack Vector

Network

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
7.4CVSS 3.1high3.13.7NVD
6.5CVSS 2.0medium86.4vuldb.com (CNA)
5.3CVSS 4.0mediumTRENDnet (CNA)
7.4CVSS 3.1highTRENDnet (CNA)
7.4CVSS 3.0highTRENDnet (CNA)
6.5CVSS 2.0mediumTRENDnet (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')

  • Execute Unauthorized Code or Commands

Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.

CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

  • Read Application Data
  • Bypass Protection Mechanism
  • Alter Execution Logic
  • Other

Mitigation: Programming languages and supporting technologies might be chosen which are not subject to these issues.

Weakness & attack patterns

  • CWE-77Command Injection
  • CWE-74

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-40 · Manipulating Writeable Terminal DevicesCAPEC-75 · Manipulating Writeable Configuration FilesCAPEC-15 · Command DelimitersCAPEC-136 · LDAP InjectionCAPEC-248 · Command InjectionCAPEC-76 · Manipulating Web Input to File System CallsCAPEC-43 · Exploiting Multiple Input Interpretation LayersCAPEC-183 · IMAP/SMTP Command Injection
  • T1562.003Impair Defenses: Impair Command History Logging
  • T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
  • T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Search application, proxy, and WAF logs for requests touching /cgi-bin/admin.cgi.
  • Prioritize edge telemetry for network-reachable TEW-823DRU.
  • Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 7.4 (AV:N)

    Aug 19, 2026 · NVD

  3. Initial · CVE published

    Aug 19, 2026 · NVD

  4. CVE published by mitre

    Aug 19, 2026 · SOCRadar CTI

  5. Reported · Advisory disclosed

    Aug 18, 2026 · TRENDnet

  6. Reported · VulDB entry created

    Aug 18, 2026 · TRENDnet

  7. Reported · VulDB entry last update

    Aug 18, 2026 · TRENDnet

References

6 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2026-75984 is TRENDnet TEW-823DRU admin.cgi command injection, a high vulnerability affecting TEW-823DRU from TRENDnet. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-75984. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.