Ac5 FirmwareOperating system · Tenda

CVE-2023-25218

CRITICAL · 9.8 CVSS v3.1 Published 2023-04-07
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 AC5 US_AC5V1.0RTL_V15.03.06.28 was discovered to contain a stack overflow via the form_fast_setting_wifi_set function. This vulnerability allows attackers to cause a Denial of Service (DoS) or execute arbitrary code via a crafted payload.

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

Stack buffer overflow in the form_fast_setting_wifi_set function of Tenda AC5 firmware US_AC5V1.0RTL_V15.03.06.28 allows remote attackers to overwrite stack memory via a crafted WiFi configuration payload, potentially achieving arbitrary code execution or causing device DoS.

MitigationApply vendor firmware patch if available; otherwise restrict network exposure to the device and disable remote management interfaces.

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
Ac5 FirmwareOperating system
Affected:= 15.03.06.28

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
    Check the device label or administrative interface for the exact model number. Confirm it is a Tenda AC5 router.
    Affected if The device is not a Tenda AC5 model.
  2. Determine the firmware version
    Access the router's web administration panel (typically at 192.168.0.1) and look in System Settings > Firmware Update or similar, or use the router's mobile app if available. Alternatively, check the firmware file name if you have access to the firmware binary.
    Affected if The firmware version is not 15.03.06.28.
  3. Check if the WiFi setup function is exposed
    Identify whether the form_fast_setting_wifi_set endpoint is accessible. This is typically accessed during initial WiFi configuration or through the WiFi settings page in the administrative interface.
    Affected if The device has already been configured and the fast setting WiFi function is not accessible.
  4. Assess network exposure
    Determine if the router's administrative interface is accessible from the WAN (Internet) side. Check port forwarding rules, remote management settings (often labeled as 'Remote Management' or 'Web Management from WAN'), and firewall rules.
    Affected if The administrative interface is only accessible from the LAN (local network) side.

A user is affected only if they have a Tenda AC5 router running firmware version 15.03.06.28 and the form_fast_setting_wifi_set function is accessible from an attacker-controlled network location.

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 patch if available; otherwise restrict network exposure to the device and disable remote management interfaces.

Fix this in Ac5 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-2023-25218 — 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-2023-25218 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