# CVE-2025-66237: Sunbird DCIM dcTrack and Power IQ Use of Hard-coded Credentials

> Attackers can use hard-coded credentials to administer the database, escalate privileges, or execute system commands on Sunbird DCIM platforms.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-4xp3-78mx-mpfq

## What is CVE-2025-66237?

CVE-2025-66237 is a high-severity vulnerability in Sunbird DCIM dcTrack, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DCIM dcTrack platforms utilize default and hard-coded credentials for access. An attacker could use these credentials to administer the database, escalate privileges on the platform or execute system commands on the host.

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

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


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

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

## Is CVE-2025-66237 being exploited?

There is no known exploitation of CVE-2025-66237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66237 is a high-severity vulnerability in Sunbird DCIM dcTrack, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66237 in the wild and no public exploit code.

Affected product: Sunbird DCIM dcTrack. 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-66237/ (Markdown: https://insights.sbomify.com/CVE-2025-66237/index.md)
```

## Sources

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

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