# CVE-2019-25322: Heatmiser Netmonitor 3.03 - Hardcoded Credentials

> Attackers can gain administrative access to Heatmiser Netmonitor devices using hardcoded default credentials, compromising device security.

- **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:** 12 Feb 2026
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-4mqf-r24p-f3vh

## What is CVE-2019-25322?

CVE-2019-25322 is a critical vulnerability in Heatmiser Netmonitor, published on 12 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heatmiser Netmonitor 3.03 contains a hardcoded credentials vulnerability in the networkSetup.htm page with predictable admin login credentials. Attackers can access the device by using the hard-coded username 'admin' and password 'admin' in the hidden form input fields.

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

## Which versions are affected by CVE-2019-25322?


## How do I fix CVE-2019-25322?

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

## Is CVE-2019-25322 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25322 and fix it if it is affected.

What it is: CVE-2019-25322 is a critical vulnerability in Heatmiser Netmonitor, published on 12 Feb 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-2019-25322 exists.

Affected product: Heatmiser Netmonitor. 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-2019-25322/ (Markdown: https://insights.sbomify.com/CVE-2019-25322/index.md)
```

## Sources

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

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