CVE-2018-25318
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 · uneditedTenda FH303/A300 firmware V5.07.68_EN contains a session weakness vulnerability that allows unauthenticated attackers to modify DNS settings by exploiting insufficient cookie validation. Attackers can send GET requests to the /goform/AdvSetDns endpoint with a crafted admin cookie to change DNS servers and redirect user traffic to malicious sites.
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 confidenceThe Tenda FH303/A300 router firmware V5.07.68_EN contains a session weakness vulnerability where the /goform/AdvSetDns endpoint fails to properly validate cookie credentials. Attackers can send unauthenticated GET requests with a crafted admin cookie to modify DNS server settings, enabling traffic redirection to malicious sites.
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= 5.07.68_en= 5.07.68_enCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label or admin interface to confirm the model is Tenda FH303 or Tenda A300Affected if Model is FH303 or A300
-
Check installed firmware versionAccess router admin panel or use `telnet`/`ssh` if enabled to retrieve firmware version; typical path is Status or Administration pageAffected if Firmware version equals 5.07.68_en exactly
-
Verify if remote administration is enabledIn router admin panel, check Remote Management or Remote Access settings (typically under Advanced or Administration tabs)Affected if Remote administration/remote management is enabled and accessible from WAN
-
Confirm DNS configuration is not manipulatedIn router admin panel, go to Advanced Settings or Network Settings and inspect Primary DNS and Secondary DNS fields under WAN or DHCP settingsAffected if DNS servers point to unexpected or attacker-controlled IP addresses or DNS settings have been changed without admin action
-
Test vulnerable endpoint accessibilityFrom an external network, attempt to access http://[router WAN IP]/goform/AdvSetDns via GET request with crafted cookie headersAffected if Endpoint responds without requiring valid authentication (indicates session validation flaw is exploitable)
A user is affected if they run exactly firmware version 5.07.68_en on an FH303 or A300 router and the router admin interface is accessible (locally or remotely), allowing the DNS settings to be modified without proper authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade the router firmware to a patched version if available; if no update exists, disable remote administration interfaces or implement network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-25318 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-25318 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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