CVE-2025-63666
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 AC15 v15.03.05.18_multi) issues an authentication cookie that exposes the account password hash to the client and uses a short, low-entropy suffix as the session identifier. An attacker with network access or the ability to run JS in a victim browser can steal the cookie and replay it to access protected resources.
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 AC15 router firmware v15.03.05.18 contains a critical authentication flaw where the session cookie exposes the account password hash to the client and uses a short, low-entropy suffix as the session identifier. An attacker with network proximity or XSS capability can steal this cookie and replay it to impersonate legitimate users and access protected administrative resources.
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= 15.03.05.18CVSS 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.
-
Verify the Tenda AC15 firmware versionLog into the router web interface (typically 192.168.0.1), navigate to System Status or Device Info page, and locate the firmware version field. Alternatively, check via UART console or SSH if enabled.Affected if The firmware version shown is exactly 15.03.05.18
-
Confirm remote management is accessible from WANLog into the router web interface and navigate to Advanced Settings, then look for 'Remote Management' or 'WAN Access' settings. Check if HTTP (port 80), HTTPS (port 443), or custom ports are enabled for WAN access. You can also test externally by scanning your public IP for open router management ports.Affected if Remote management is enabled and accessible from WAN/outside network
-
Inspect authentication cookie structureLog into the router web interface and use browser developer tools (F12) to view Cookies under Application or Storage tab. Look for session cookies and examine their value structure. Check if the cookie contains a readable hash or password-like string embedded in the value.Affected if The authentication cookie contains a password hash or similar credential-derived string in plain text
You are affected if your Tenda AC15 runs firmware version 15.03.05.18 and either remote management is exposed to untrusted networks or an XSS vulnerability exists that could allow cookie theft.
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 dataApply vendor firmware patch when available; if no patch exists, consider replacing the device with a model from a vendor providing timely security updates, and implement network segmentation to limit exposure to untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63666 — 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-2025-63666 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