dbcve.org
Ac1206 FirmwareOperating system · Tenda

CVE-2025-10432

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
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
A vulnerability was found in Tenda AC1206 15.03.06.23. This vulnerability affects the function check_param_changed of the file /goform/AdvSetMacMtuWa of the component HTTP Request Handler. Performing manipulation of the argument wanMTU results in stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been made public and could be used.

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 stack-based buffer overflow vulnerability exists in the Tenda AC1206 router firmware (15.03.06.23) within the HTTP Request Handler's /goform/AdvSetMacMtuWa endpoint. The check_param_changed function fails to perform proper bounds checking on the wanMTU parameter before copying it to a fixed-size stack buffer, allowing remote attackers to overwrite return addresses and execute arbitrary code.

MitigationApply vendor firmware patches when available; meanwhile, disable remote web management interfaces, place device behind a firewall restricting HTTP/HTTPS access from untrusted 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
Ac1206 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. Confirm firmware version
    Access the router admin interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version. Alternatively, use the router's web API or check via telnet/SSH if available: 'cat /proc/version' or '固件版本' in the admin panel.
    Affected if The installed firmware version is exactly 15.03.06.23
  2. Verify vulnerable endpoint exists
    Attempt to access the URL path /goform/AdvSetMacMtuWa on the router's web interface (e.g., http://router-ip/goform/AdvSetMacMtuWa). The endpoint may respond even if the parameter is not actively configurable.
    Affected if The endpoint responds with any HTTP content, indicating the vulnerable function is present in the firmware.
  3. Check if remote web management is enabled
    In the router admin interface, locate the Remote Management or Web Server settings (often under Advanced Settings, System Tools, or Security). Verify if 'Remote Web Management', 'Remote Access', or 'Allow external access to web interface' is enabled.
    Affected if Remote web management is enabled, allowing unauthenticated or low-privilege attackers to reach the vulnerable endpoint from the WAN.
  4. IdentifywanMTU parameter exposure
    Inspect the HTML form at /goform/AdvSetMacMtuWa or related MTU configuration pages. Look for an input field named 'wanMTU' or similar that accepts numeric values for MTU configuration.
    Affected if The wanMTU parameter field exists in the web interface and accepts user-supplied input without visible length validation.

A user is affected if the Tenda AC1206 firmware is version 15.03.06.23, the vulnerable endpoint is accessible, and remote web management is enabled, allowing WAN-side exploitation of the wanMTU buffer overflow.

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 vendor firmware patches when available; meanwhile, disable remote web management interfaces, place device behind a firewall restricting HTTP/HTTPS access from untrusted networks, and monitor for indicators of compromise.

Fix this in Ac1206 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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