# CVE-2026-24444: SDMC NE6037 Hardcoded Password via mgmt.php/npcmd.php

> Unauthenticated attackers can use hardcoded credentials in recovery endpoints to gain root access and enable remote services on SDMC NE6037 routers.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2026
- **Updated:** 28 May 2026
- **Also known as:** GHSA-cg6m-frf7-6623

## What is CVE-2026-24444?

CVE-2026-24444 is a critical vulnerability in SDMC Technology Co., Ltd NE6037, published on 28 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SDMC NE6037 cable modem routers running firmware 7.1.6.0.25 and 7.1.6.1.9_B9 contain a hardcoded password vulnerability in the web management interface recovery endpoints (mgmt.php, npcmd.php) that allows unauthenticated attackers to gain root access by submitting the hardcoded credential to the recovery endpoint via HTTP. Attackers can leverage this hardcoded password to enable filtered SSH and Telnet services on the device, resulting in unauthenticated root-level remote access to the underlying system.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-24444?


## How do I fix CVE-2026-24444?

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

## Is CVE-2026-24444 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24444 and fix it if it is affected.

What it is: CVE-2026-24444 is a critical vulnerability in SDMC Technology Co., Ltd NE6037, published on 28 May 2026. 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-2026-24444 exists.

Affected product: SDMC Technology Co., Ltd NE6037. 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-2026-24444/ (Markdown: https://insights.sbomify.com/CVE-2026-24444/index.md)
```

## Sources

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

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