dbcve.org
Ac15 FirmwareOperating system · Tenda

CVE-2026-24105

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-02
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
Public exploit 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
An issue was discovered in goform/formsetUsbUnload in Tenda AC15V1.0 V15.03.05.18_multi. The value of `v1` was not checked, potentially leading to a command injection vulnerability if injected into doSystemCmd.

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

A command injection vulnerability exists in Tenda AC15 V1.0 firmware V15.03.05.18_multi in the /goform/formsetUsbUnload endpoint. The v1 parameter is passed unsanitized to the doSystemCmd function, allowing unauthenticated remote attackers to execute arbitrary system commands by injecting shell metacharacters.

MitigationRestrict web management interface access to LAN only (disable WAN access via firewall rules), and apply vendor firmware patches when available. If patching is not possible, consider replacing the device.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ac15 FirmwareOperating system
Affected:= 15.03.05.18

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 AC15 V1.0 model.
    Affected if The device is not a Tenda AC15 V1.0, the vulnerability does not apply.
  2. Check the firmware version
    Log into the router web interface and navigate to System Settings > Firmware Upgrade or check the version displayed on the administration page. Alternatively, use the router's admin panel or telnet/ssh to retrieve the firmware version.
    Affected if The firmware version is exactly 15.03.05.18 (the multi-region build), indicating the device is affected.
  3. Verify the web management interface is accessible
    Attempt to access the router's web interface from an external network (WAN) by navigating to the router's public IP address on port 80 or 443. Check router firewall settings to determine if WAN management access is permitted.
    Affected if The router web interface is exposed to the WAN (internet), meaning the vulnerability is remotely exploitable without LAN access.
  4. Confirm USB functionality is configured
    Check if a USB storage device is attached to the router and if USB sharing features are enabled in the router web interface under USB Settings or Storage settings.
    Affected if USB is enabled and a USB device is attached, as the vulnerable endpoint /goform/formsetUsbUnload handles USB device management.
  5. Check for the vulnerable endpoint
    Send an HTTP GET or POST request to http://[router-ip]/goform/formsetUsbUnload and verify the endpoint responds. This can be done using curl: curl -X POST http://[router-ip]/goform/formsetUsbUnload
    Affected if The endpoint responds, indicating it is present and potentially exploitable if other conditions are met.

A user is affected if they have a Tenda AC15 V1.0 router running firmware version 15.03.05.18 with the web interface accessible (especially from WAN) and the vulnerable endpoint exposed.

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

Restrict web management interface access to LAN only (disable WAN access via firewall rules), and apply vendor firmware patches when available. If patching is not possible, consider replacing the device.

Fix this in Ac15 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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