CVE-2026-38063
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_radio_on_with_ia_apn via the ia 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 confidenceThe Tenda 5G03 router firmware V05.03.02.04 contains an OS command injection vulnerability in the `action_radio_on_with_ia_apn` function. The `ia` parameter is not sanitized before being passed to a system call, allowing unauthenticated remote attackers to execute arbitrary operating system commands on the device.
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 admin interface or check the device label/marketing materials to confirm the exact model number is Tenda 5G03Affected if The device is a Tenda 5G03 router
-
Determine the installed firmware versionLog into the router web管理界面 and navigate to System Settings, System Info, or Firmware Upgrade section to view the current firmware versionAffected if The firmware version is V05.03.02.04 or any version within the affected range (prior to vendor patch)
-
Verify management interface network exposureCheck the router's WAN/LAN interface settings and firewall rules to determine if the web管理界面 (typically port 80/443) is accessible from WAN/untrusted networksAffected if The router management interface is exposed to the internet or untrusted LAN segments without authentication barriers
-
Confirm the vulnerable function is presentInspect the firmware filesystem or web interface for the presence of the 'action_radio_on_with_ia_apn' function by examining HTTP endpoints or binary componentsAffected if The firmware contains the unauthenticated web endpoint that processes the 'ia' parameter without sanitization
A user is affected if they are running Tenda 5G03 firmware V05.03.02.04 (or an unpatched version within the affected range) with the management interface exposed to untrusted networks.
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 updates when available; if no patch exists, restrict or disable the affected management interface from untrusted networks, as the CVSS indicates network-exploitable unauthenticated access.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38063 — 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-38063 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