Ac6 FirmwareOperating system · Tenda

CVE-2025-24322

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-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
An unsafe default authentication vulnerability exists in the Initial Setup Authentication functionality of Tenda AC6 V5.0 V02.03.01.110. A specially crafted network request can lead to arbitrary code execution. An attacker can browse to the device to trigger this vulnerability.

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 · moderate confidence

Tenda AC6 V5.0 V02.03.01.110 contains an unsafe default authentication vulnerability in its Initial Setup Authentication functionality. Attackers can send specially crafted network requests to the device to bypass authentication and achieve arbitrary code execution.

MitigationApply the latest vendor firmware update for Tenda AC6. If no update is available, restrict network access to the device's management interface and monitor for unauthorized access attempts.

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
Ac6 FirmwareOperating system
Affected:= 02.03.01.110

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
    Log into the Tenda router web interface or check the device label to confirm it is an AC6 model
    Affected if Device is not a Tenda AC6 model, then it is not affected by this specific CVE
  2. Check the installed firmware version
    Access the router's web management interface (typically at 192.168.0.1), navigate to System Settings or Firmware Upgrade section, and record the firmware version displayed
    Affected if Firmware version is exactly 02.03.01.110, indicating the device is running the affected version
  3. Verify Initial Setup Authentication accessibility
    Attempt to access the Initial Setup page via HTTP/HTTPS request to the router (commonly /index.html or /setup), or check if the device still presents first-time setup wizard without requiring authentication
    Affected if Initial Setup Authentication is accessible without credentials or the setup wizard is still active, indicating the vulnerability may be exploitable
  4. Check network exposure of management interface
    Determine if the router's web interface is accessible from external networks (WAN side) by attempting to access the router's public IP on ports 80/443, or review port forwarding/firewall rules
    Affected if Management interface is exposed to untrusted networks, increasing exploitability risk

If the device is a Tenda AC6 running firmware version 02.03.01.110 and the Initial Setup Authentication is accessible, the environment is affected by CVE-2025-24322.

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

Apply the latest vendor firmware update for Tenda AC6. If no update is available, restrict network access to the device's management interface and monitor for unauthorized access attempts.

Fix this in Ac6 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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