# CVE-2025-64308: Brightpick Mission Control / Internal Logic Control Unprotected Transport of Credentials

> Hardcoded credentials in client-side JavaScript expose documentation portal access, allowing attackers to bypass authentication and read sensitive data.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Nov 2025
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-wj9f-8875-4rpw

## What is CVE-2025-64308?

CVE-2025-64308 is a high-severity vulnerability in Brightpick Mission Control / Internal Logic Control, published on 14 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Brightpick Mission Control web application exposes hardcoded credentials in its client-side JavaScript bundle to Brightpick AI's documentation portal.

Weakness: CWE-523 (Unprotected Transport of Credentials)

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


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

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

## Is CVE-2025-64308 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64308 is a high-severity vulnerability in Brightpick Mission Control / Internal Logic Control, published on 14 Nov 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-64308 in the wild and no public exploit code.

Affected product: Brightpick Mission Control / Internal Logic Control. 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-64308/ (Markdown: https://insights.sbomify.com/CVE-2025-64308/index.md)
```

## Sources

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

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