# CVE-2025-66238: Sunbird DCIM dcTrack and Power IQ Authentication Bypass Using an Alternate Path or Channel

> An authenticated user can bypass authentication restrictions to access restricted services or data on the host machine via virtual console features.

- **Severity:** High 7.4 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-q579-mcrq-q4vr

## What is CVE-2025-66238?

CVE-2025-66238 is a high-severity authentication bypass vulnerability in Sunbird DCIM dcTrack, published on 4 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

DCIM dcTrack allows an attacker to misuse certain remote access features. An authenticated user with access to the appliance's virtual console could exploit these features to redirect network traffic, potentially accessing restricted services or data on the host machine.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-66238 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66238 is a high-severity authentication bypass vulnerability in Sunbird DCIM dcTrack, published on 4 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66238 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-66238/ (Markdown: https://insights.sbomify.com/CVE-2025-66238/index.md)
```

## Sources

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

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