W309r FirmwareOperating system · Tenda

CVE-2018-25317

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-29
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
Tenda W3002R/A302/W309R wireless routers version V5.07.64_en contain a cookie session weakness vulnerability that allows unauthenticated attackers to modify DNS settings by exploiting insufficient session validation. Attackers can send GET requests to the /goform/AdvSetDns endpoint with a crafted admin language cookie to change primary and secondary DNS servers, redirecting user traffic to malicious DNS servers.

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

Tenda W3002R/A302/W309R wireless routers firmware V5.07.64_en contain an unauthenticated cookie session validation weakness in the /goform/AdvSetDns endpoint. Attackers can send crafted GET requests with a modified admin language cookie to bypass session checks and modify primary/secondary DNS server settings, enabling traffic redirection to attacker-controlled DNS servers.

MitigationRestrict access to the router administrative interface from untrusted networks using firewall rules or network segmentation; monitor for unauthorized DNS configuration changes; contact Tenda for firmware patch availability.

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
W309r FirmwareOperating system
Affected:= 5.07.64_en
A302 FirmwareOperating system
Affected:= 5.07.64_en
W3002r FirmwareOperating system
Affected:= 5.07.64_en

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 router model and firmware version
    Access the router web interface or use commands like 'nvram show' or check the admin page for the exact firmware version displayed. Look for model numbers W3002R, A302, or W309R.
    Affected if The router is a Tenda W3002R, A302, or W309R with firmware version exactly 5.07.64_en
  2. Verify web interface accessibility
    Attempt to access the router administrative interface over HTTP/HTTPS on the LAN or WAN interface. Check if the login page or /goform/ endpoints respond.
    Affected if The router web interface is reachable from an untrusted network (WAN) or the device has no network access controls limiting admin interface exposure
  3. Inspect current DNS server configuration
    Navigate to the router admin panel DNS settings page, or use command-line tools like 'nslookup' with 'server' command to query the router's DNS, or check via 'cat /etc/resolv.conf' on the router if SSH/telnet access is available.
    Affected if Primary or secondary DNS servers are set to IP addresses you did not configure, or DNS settings show unexpected values pointing to unknown servers
  4. Test /goform/AdvSetDns endpoint response
    Send a GET request to http://<router-ip>/goform/AdvSetDns using curl or a browser. Observe if the endpoint responds without requiring authentication.
    Affected if The endpoint returns a response (even an error) without redirecting to a login page, indicating the session validation weakness is present

You are affected if you have a Tenda W3002R, A302, or W309R router running firmware version 5.07.64_en, the router web interface is exposed, and DNS settings show unexpected values or the /goform/AdvSetDns endpoint is accessible without authentication.

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

Restrict access to the router administrative interface from untrusted networks using firewall rules or network segmentation; monitor for unauthorized DNS configuration changes; contact Tenda for firmware patch availability.

Fix this in W309r Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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