CVE-2026-38061
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_volume via the volume 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 a command injection vulnerability in the action_set_volume function. The volume parameter passed to this function is not properly sanitized, allowing an attacker to inject arbitrary OS commands by crafting malicious input. This can lead to full compromise of 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.
-
Confirm device model is Tenda 5G03Access the router web interface or check the device label/menu for the model numberAffected if Device is a Tenda 5G03 router
-
Check firmware versionLog into the router admin panel and navigate to System Settings or Status page to view the firmware version, or use telnet/SSH if enabled to run 'cat /proc/version' or check /etc/versionAffected if Firmware version is V05.03.02.04
-
Verify web management interface is accessibleAttempt to access the router login page from the network (http://<router-ip>/)Affected if Web interface responds and is reachable from the network segment being tested
-
Check if unauthenticated endpoints are exposedSend an HTTP POST request to /goform/action_set_volume (or similar endpoint) without authentication credentials and observe the responseAffected if The endpoint accepts requests without authentication and processes the volume parameter
-
Confirm the volume parameter accepts shell inputSend a crafted POST request to the affected endpoint with shell metacharacters in the volume parameter (e.g., volume=;ls) and check if command execution occursAffected if The device executes injected shell commands in the response or shows evidence of command execution
The device is affected if it is a Tenda 5G03 router running firmware V05.03.02.04 with an accessible web management interface that exposes the unauthenticated action_set_volume endpoint.
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 network segmentation to isolate the affected router from sensitive network segments and restrict management interface access to trusted IPs only. Monitor for indicator of compromise. The definitive fix requires a vendor-supplied firmware update that properly sanitizes input in the action_set_volume function.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38061 — 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-38061 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