dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-38064

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-15
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
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
Tenda 5G03 V05.03.02.04 (Version 1.0) is vulnerable to Command injection in the function action_dial_call via the dialNumber parameter.

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

Tenda 5G03 router firmware V05.03.02.04 contains a command injection vulnerability in the web interface function action_dial_call. The dialNumber parameter is not properly sanitized, allowing attackers to inject arbitrary OS commands. This unauthenticated vulnerability with CVSS 9.8 can lead to complete device compromise.

MitigationApply vendor firmware patch when available; until then, isolate device from untrusted networks and disable remote management interfaces if not required.

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
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 the device model
    Access the router web interface or check the device label to confirm it is a Tenda 5G03 router
    Affected if The device is NOT a Tenda 5G03 router - you are not affected by this specific CVE
  2. Check the firmware version
    Log into the router web interface and look for the firmware version in the system status or administration settings, or check via telnet/SSH if available
    Affected if The installed firmware version is V05.03.02.04 - you are directly affected
  3. Verify web management interface accessibility
    Attempt to access the router web interface from the network where the device is deployed (typically http://192.168.0.1 or similar)
    Affected if The web interface is reachable from an untrusted network - you are exposed to the vulnerability
  4. Check if remote management is enabled
    In the router web interface, navigate to advanced settings or remote management and verify whether remote HTTP/HTTPS access is permitted from WAN
    Affected if Remote management from WAN is enabled - the vulnerability is exploitable from outside the local network

You are affected if you have a Tenda 5G03 router running firmware V05.03.02.04 with its web interface accessible, especially if remote management is enabled.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch when available; until then, isolate device from untrusted networks and disable remote management interfaces if not required.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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