CVE-2019-6725
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 · uneditedThe rpWLANRedirect.asp ASP page is accessible without authentication on ZyXEL P-660HN-T1 V2 (2.00(AAKK.3)) devices. After accessing the page, the admin user's password can be obtained by viewing the HTML source code, and the interface of the modem can be accessed as admin.
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 confidenceUnauthenticated access to the rpWLANRedirect.asp ASP page on ZyXEL P-660HN-T1 V2 routers exposes the admin password in plaintext within the HTML source code, allowing full unauthorized admin access to the device management interface.
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= 2.00\(aakk.3\)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.0/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 the router modelAccess the router's web interface or check the device label to confirm the model is ZyXEL P-660HN-T1 V2Affected if The device is a ZyXEL P-660HN-T1 V2 router
-
Check the firmware versionLog into the router admin interface and navigate to Status or Management pages to view the firmware version, or check the device label for firmware version markingAffected if The firmware version is exactly 2.00(aakk.3)
-
Access the vulnerable ASP pageFrom a browser on a network connected to the router, navigate to http://[router-ip]/rpWLANRedirect.asp without providing any login credentialsAffected if The page loads without requiring authentication
-
Inspect HTML source for plaintext passwordRight-click on the loaded rpWLANRedirect.asp page, select 'View Page Source' or 'Inspect Element', and search for password-related fields or the actual admin password in plaintextAffected if The admin password is visible in plaintext within the HTML source code
The device is affected if it is a ZyXEL P-660HN-T1 V2 router running firmware version 2.00(aakk.3) and the rpWLANRedirect.asp page is accessible without authentication, exposing the admin password in the HTML source.
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 dataRestrict access to the router's web management interface to trusted networks only; if available, apply vendor firmware update; otherwise consider replacing the end-of-life device.
- Consultation4.0 h
- Implementation8.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 $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-6725 — 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-2019-6725 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