CVE-2025-43986
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 · uneditedAn issue was discovered on KuWFi GC111 GC111-GL-LM321_V3.0_20191211 devices. The TELNET service is enabled by default and exposed over the WAN interface without authentication.
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 KuWFi GC111 router (firmware GC111-GL-LM321_V3.0_20191211) has TELNET service enabled by default and exposed on the WAN interface without any authentication. This allows remote unauthenticated attackers from the internet to connect to port 23 and gain shell access to the device, potentially leading to full device compromise.
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
- 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 device modelAccess the router administration interface or check the device label to confirm the model is KuWFi GC111Affected if The device is not a KuWFi GC111 router, then this specific CVE does not apply
-
Check firmware versionAccess router admin panel or use command like 'cat /proc/version' or check via web UI firmware version page to determine the installed firmware versionAffected if The firmware version is GC111-GL-LM321_V3.0_20191211 or earlier (older versions)
-
Verify TELNET service is enabledFrom a computer on the local network, attempt to connect to the router via TELNET on port 23 (e.g., 'telnet <LAN_IP>' or use nmap: 'nmap -p 23 <LAN_IP>')Affected if Port 23 is open and responds to TELNET connection attempts, indicating the service is enabled
-
Confirm TELNET is exposed on WAN interfaceFrom an external network or using an online port scanner, test connectivity to the router's public/WAN IP on port 23 (e.g., 'nmap -p 23 <WAN_IP>')Affected if Port 23 is accessible from the internet (WAN side) on the router's public IP address
-
Test TELNET authentication requirementAttempt to connect via TELNET from WAN without providing any credentials to see if access is granted without authenticationAffected if TELNET connection completes and provides shell access without prompting for username or password
If the device is a KuWFi GC111 router with firmware version GC111-GL-LM321_V3.0_20191211 or earlier, and port 23 is accessible from the WAN without requiring authentication, the environment is affected by this CVE.
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 dataDisable the TELNET service entirely via the device administration interface, or if TELNET is required internally, configure the built-in firewall to block all WAN-facing access to TCP port 23.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43986 — 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-43986 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