CVE-2025-52376
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 authentication bypass vulnerability in the /web/um_open_telnet.cgi endpoint in Nexxt Solutions NCM-X1800 Mesh Router firmware UV1.2.7 and below, allowing an attacker to remotely enable the Telnet service without authentication, bypassing security controls. The Telnet server is then accessible with hard-coded credentials, allowing attackers to gain administrative shell access and execute arbitrary commands on the device.
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 confidenceAn authentication bypass vulnerability in the /web/um_open_telnet.cgi endpoint of Nexxt Solutions NCM-X1800 Mesh Router firmware UV1.2.7 and below allows remote unauthenticated attackers to enable the Telnet service, bypassing all security controls. The Telnet service uses hard-coded credentials, granting attackers administrative shell access and the ability to execute arbitrary commands on the device.
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 modelCheck the device label, web interface, or administrative console for the exact model number to confirm it is a Nexxt Solutions NCM-X1800 Mesh RouterAffected if Device is not an NCM-X1800 model
-
Check firmware versionAccess the router web interface or administrative console and locate the firmware version information, typically found in System Settings, Status, or About pages. Compare the installed version to UV1.2.7Affected if Firmware version is UV1.2.7 or below
-
Verify Telnet service statusFrom the internal network, attempt to connect to port 23 (Telnet) on the device IP address using a telnet client or netcat command: nc -v <device_ip> 23Affected if Telnet service is responding on the device
-
Inspect the vulnerable endpointFrom a system on the same network, attempt to access the URL http://<device_ip>/web/um_open_telnet.cgi using a web browser or curl command and observe the HTTP responseAffected if Endpoint is accessible and returns a successful response without authentication
-
Review network exposureCheck router firewall rules, port forwarding settings, or external scan results to determine if the web management interface (port 80/443) and Telnet port (23) are exposed to untrusted networks or the internetAffected if Management interface or Telnet service is accessible from external networks
The device is affected if it is a Nexxt Solutions NCM-X1800 Mesh Router running firmware UV1.2.7 or below, and the /web/um_open_telnet.cgi endpoint is accessible or Telnet service is enabled on the device.
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 the latest firmware update from Nexxt Solutions if available; if no patch exists, disable or block Telnet at the network perimeter and implement strict access controls to prevent external access to the affected endpoint.
- Consultation4.0 h
- Implementation2.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,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52376 — 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-52376 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