CVE-2026-38062
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 · uneditedTenda 5G03 V05.03.02.04 (Version 1.0) is vulnerable to Command injection in the function action_set_rat_mode via the ratMode 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 confidenceA command injection vulnerability exists in the Tenda 5G03 router firmware version V05.03.02.04. The ratMode parameter passed to the action_set_rat_mode function is not properly sanitized before being used in a system call, allowing an attacker to inject arbitrary shell commands with root privileges.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the router's web management interface or check the device label/marketing materials to confirm the model is Tenda 5G03Affected if The device is not a Tenda 5G03 router - different models are not affected by this specific vulnerability
-
Check the installed firmware versionLog into the router web interface and navigate to System Settings or Administration > Firmware Upgrade, or use the command line (if accessible) to retrieve the firmware versionAffected if The firmware version is exactly V05.03.02.04 - only this specific version contains the vulnerable code
-
Verify if the web management interface is accessibleAttempt to reach the router's HTTP/HTTPS management portal from a network client (typically at the router's LAN IP such as 192.168.0.1 or 192.168.1.1)Affected if The web interface is accessible - the command injection occurs in the action_set_rat_mode function within the web binary, so the management UI must be reachable for exploitation
-
Confirm the vulnerable parameter is exposedCheck if the router responds to requests at the rat_mode endpoint or similar path (typically /goform/ or /cgi-bin/ endpoint handling the ratMode parameter)Affected if The specific endpoint handling the ratMode parameter is publicly accessible - this is the attack vector for injecting commands through the action_set_rat_mode function
You are affected if you have a Tenda 5G03 router running firmware version V05.03.02.04 with its web management interface and the ratMode parameter endpoint accessible to an attacker
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware patch if available; otherwise restrict network access to the router's management interface and implement input validation on the ratMode parameter in the web binary.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-38062 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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