Ac10 FirmwareOperating system · Tenda

CVE-2025-25674

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 is vulnerable to Buffer Overflow in form_fast_setting_wifi_set via the parameter ssid.

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 buffer overflow vulnerability exists in the Tenda AC10 V1.0 router firmware V15.03.06.23 within the form_fast_setting_wifi_set function. The vulnerability is triggered through the ssid parameter, allowing an attacker to overflow a buffer and potentially achieve remote code execution on the device.

MitigationApply the vendor-provided firmware patch when available. Until then, restrict administrative web interface access to trusted networks and monitor for indicators of compromise.

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 device model
    Check the router label or log into the web admin interface and navigate to System Status or Device Info to confirm the model is Tenda AC10 V1.0
    Affected if Device is not a Tenda AC10 V1.0 router - this vulnerability does not apply
  2. Check firmware version
    In the web admin interface, go to System Settings > Firmware Upgrade or System Status page and note the firmware version displayed
    Affected if Firmware version is exactly 15.03.06.23 - this specific version is affected
  3. Verify web interface accessibility
    Attempt to access the router web admin interface from a browser using the router IP address (typically 192.168.0.1 or 192.168.1.1)
    Affected if Web interface is accessible over untrusted networks (WAN) - the vulnerable form_fast_setting_wifi_set function is exposed
  4. Confirm remote management status
    In the web admin interface, go to Advanced Settings > Remote Management or similar section and check if remote web management is enabled
    Affected if Remote management is enabled and the web interface is WAN-accessible - attacker can reach the vulnerable ssid parameter

A user is affected if they have a Tenda AC10 V1.0 router running firmware version 15.03.06.23 with the web admin interface accessible from untrusted networks.

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 vendor-provided firmware patch when available. Until then, restrict administrative web interface access to trusted networks and monitor for indicators of compromise.

Fix this in Ac10 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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