CVE-2025-12386
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 · uneditedPix-Link LV-WR21Q does not enforce any form of authentication for endpoint /goform/getHomePageInfo. Remote unauthenticated attacker is able to use this endpoint to e.g: retrieve cleartext password to the access point. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version V108_108 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.
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 · moderate confidenceThe Pix-Link LV-WR21Q router has a missing authentication vulnerability on the /goform/getHomePageInfo endpoint. This allows any remote attacker without credentials to access this API and retrieve sensitive configuration data including cleartext WiFi passwords. This is an information disclosure vulnerability with CVSS 6.9 indicating moderate severity due to network-exploitable unauthenticated access to plaintext credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 device modelAccess the router web interface or check the device label/marketing material to confirm the model is Pix-Link LV-WR21QAffected if Device model is Pix-Link LV-WR21Q and the firmware has not been updated to address this vulnerability
-
Verify web interface accessibilityAttempt to access the router's HTTP/HTTPS web interface from a network-connected host. Try accessing the base IP address of the router in a browserAffected if The router web interface is reachable from an untrusted network (not just the local LAN)
-
Test unauthenticated endpoint accessSend an HTTP GET or POST request to http://[router-ip]/goform/getHomePageInfo without providing any authentication credentials or session cookiesAffected if The request returns an HTTP 200 response with JSON or other data instead of requiring login (HTTP 401 or redirect to login page)
-
Check for sensitive data disclosureExamine the response from /goform/getHomePageInfo for WiFi network names (SSIDs), WiFi passwords in plaintext, or other configuration parameters that should be protectedAffected if The endpoint returns WiFi passwords or other sensitive configuration in plaintext without authentication
A user is affected if they have a Pix-Link LV-WR21Q router where the /goform/getHomePageInfo endpoint responds without authentication and exposes WiFi passwords or other sensitive configuration data.
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 dataSince no vendor patch is available, network exposure should be minimized by not exposing the device management interface to the internet, and network segmentation should isolate IoT devices from critical infrastructure. Consider replacing with a vendor-supported device.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12386 — 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-12386 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