Ac10 FirmwareOperating system · Tenda

CVE-2025-25675

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-20
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
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
Tenda AC10 V1.0 V15.03.06.23 has a command injection vulnerablility located in the formexeCommand function. The str variable receives the cmdinput parameter from a POST request and is later assigned to the cmd_buf variable, which is directly used in the doSystemCmd function, causing an arbitrary command execution.

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

Tenda AC10 V1.0 firmware V15.03.06.23 contains a command injection vulnerability in the formexeCommand function. The cmdinput parameter from POST requests is assigned to the str variable, then to cmd_buf, and passed directly to doSystemCmd without sanitization, allowing arbitrary OS command execution.

MitigationUpgrade to a patched firmware version if available; otherwise, restrict network access to the device's web administration interface or replace the device if end-of-life.

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
Ac10 FirmwareOperating system
Affected:= 15.03.06.23

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 and firmware version
    Access the device web interface or check via telnet/SSH, then navigate to System Settings > Firmware Version or use the 'ver' command via UART serial connection to retrieve the exact firmware version string.
    Affected if The firmware version is exactly 15.03.06.23 for Tenda AC10 V1.0 hardware revision.
  2. Verify the web management interface is accessible
    Attempt to reach the device's HTTP/HTTPS web interface on the LAN IP address or WAN IP if remote management is enabled. Confirm the Tenda login page loads successfully.
    Affected if The web interface responds and shows the Tenda AC10 login page.
  3. Confirm authentication is possible
    Check if default administrative credentials (admin:admin or admin:password) are still in use, or determine if valid admin session cookies/tokens can be obtained through login.
    Affected if Default credentials grant administrative access or valid admin authentication tokens can be obtained.
  4. Check if the formexeCommand endpoint is present
    Send a POST request to /cgi-bin/formexeCommand with a cmdinput parameter (e.g., cmdinput=test) and observe the response. This endpoint handles the vulnerable function.
    Affected if The device returns a response (even an error) indicating the formexeCommand handler exists.
  5. Determine network exposure of management interface
    Review device network configuration to check if remote management (WAN access) is enabled, or verify if the LAN interface is accessible to untrusted network segments.
    Affected if The web interface is reachable from WAN or from network segments outside the trusted LAN.

A user is affected if they are running Tenda AC10 firmware version 15.03.06.23 and the web management interface is accessible with valid credentials or default credentials.

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

Upgrade to a patched firmware version if available; otherwise, restrict network access to the device's web administration interface or replace the device if end-of-life.

Fix this in Ac10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-25675 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-25675 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