A18 FirmwareOperating system · Tenda

CVE-2026-2877

HIGH · 8.8 CVSS v3.1 Published 2026-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 has been found in Tenda A18 15.13.07.13. This affects the function strcpy of the file /goform/WifiExtraSet of the component Httpd Service. The manipulation of the argument wpapsk_crypto5g leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may 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 Tenda A18 router firmware version 15.13.07.13 within the Httpd service's /goform/WifiExtraSet function. The strcpy function copies the wpapsk_crypto5g parameter to a stack buffer without length validation, allowing remote attackers to overwrite stack memory and potentially execute arbitrary code.

MitigationIf vendor firmware update available, apply immediately. Otherwise, restrict network access to the device's management interface via firewall rules or disable remote administration. Consider device replacement if no patch is forthcoming.

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
A18 FirmwareOperating system
Affected:= 15.13.07.13

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Tenda A18 device model
    Access the device's web administration interface or check the device label/metadata to confirm the model is Tenda A18
    Affected if Device is not a Tenda A18 extender, then not affected by this specific CVE
  2. Check firmware version
    Log into the Tenda A18 web interface and navigate to System Settings > Firmware Upgrade, or use the device's administrative CLI if available, to identify the installed firmware version
    Affected if Firmware version is 15.13.07.13 exactly - this is the only affected version
  3. Verify httpd web service is running
    Check if the httpd process is running on the device, typically accessible via the web interface on port 80 or 443
    Affected if httpd is running and the web interface is accessible, making the attack surface active
  4. Confirm WifiExtraSet endpoint exists
    Attempt to access or inspect the /goform/WifiExtraSet function in the httpd web service binary or documentation
    Affected if The WifiExtraSet function exists and accepts the wpapsk_crypto5g parameter, enabling the vulnerable code path
  5. Check web management interface exposure
    Determine if the device's web interface is exposed to untrusted networks (WAN) or only accessible from the local network (LAN)
    Affected if The web management interface is externally accessible, increasing the risk of remote exploitation

The environment is affected only if the device is a Tenda A18 running exactly firmware version 15.13.07.13 with the httpd web service accessible and the /goform/WifiExtraSet endpoint present.

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

If vendor firmware update available, apply immediately. Otherwise, restrict network access to the device's management interface via firewall rules or disable remote administration. Consider device replacement if no patch is forthcoming.

Fix this in A18 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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