# CVE-2025-52376: Auth bypass in n/a

> Attackers can bypass authentication to enable Telnet and gain administrative shell access on Nexxt Solutions Mesh Routers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2025
- **Updated:** 15 Jul 2025
- **Also known as:** GHSA-932h-pf5w-9584

## What is CVE-2025-52376?

CVE-2025-52376 is a critical authentication bypass vulnerability in n/a, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-52376?


## How do I fix CVE-2025-52376?

No fix has been published for CVE-2025-52376 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-52376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52376 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52376 and fix it if it is affected.

What it is: CVE-2025-52376 is a critical authentication bypass vulnerability in n/a, published on 15 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52376 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-52376/ (Markdown: https://insights.sbomify.com/CVE-2025-52376/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-52376
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-52376
- OSV: https://osv.dev/vulnerability/CVE-2025-52376

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-52376/
Summaries are generated and may contain mistakes; the official description above is the record.