CVE-2026-38060
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_unlock_sim via the pin 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_unlock_sim function. The pin parameter is directly passed to a system command without sanitization, allowing an attacker to inject arbitrary shell commands.
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; alternatively, use Nmap or SSH to query the device and look for 'Tenda' or '5G03' in the HTTP response headers, SNMP sysDescr, or login page source.Affected if The device is not a Tenda 5G03 router, then this specific CVE does not apply.
-
Identify installed firmware versionLog into the router web interface and navigate to System Settings or Status page to view firmware version; alternatively, use 'cat /proc/version' or check '/etc/version' via SSH/Telnet if shell access is available.Affected if The firmware version is V05.03.02.04, matching the vulnerable version exactly.
-
Check if web management interface is accessibleAttempt HTTP/HTTPS access to the router's LAN IP address (typically 192.168.0.1 or 192.168.1.1); verify the login page loads successfully.Affected if The web interface is reachable on the network, exposing the vulnerable function to attackers who can reach the router's web service.
-
Verify action_unlock_sim endpoint existsLocate the SIM card or mobile network settings page in the router web interface; look for a SIM unlock or PIN unlock feature. If the page exists, the underlying CGI script '/cgi-bin/VoIP_.' (or similar) handling 'action_unlock_sim' is likely present.Affected if The SIM unlock feature is present and enabled in the router firmware, meaning the vulnerable code path is available for exploitation.
-
Confirm pin parameter is accepted by the deviceIf you have access, examine the HTTP POST request when submitting a PIN in the SIM unlock form; note that the 'pin' parameter is passed directly to the backend handler without visible sanitization in the request.Affected if The pin parameter is accepted directly by the router's web interface, confirming the injection point exists.
You are affected if your Tenda 5G03 router runs firmware version V05.03.02.04 and exposes the web management interface with the SIM unlock feature enabled.
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-supplied firmware patch when available; until then, disable or restrict access to the vulnerable function and minimize the router's network exposure.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.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 $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38060 — 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-38060 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