# CVE-2025-65957: Core Bot is Leaking Sensitive Credentials in Logs, Errors, and Messages

> An attacker can read sensitive API keys and tokens from logs or error messages in the Core Bot Discord application.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:L/SI:H/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-42j6-x28v-38r8

## What is CVE-2025-65957?

CVE-2025-65957 is a high-severity vulnerability in Intercore-Productions Core-Bot, published on 25 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Core Bot Is an Open Source discord bot made for maple hospital servers. Prior to commit dffe050, the API keys (SUPABASE_API_KEY, TOKEN) are loaded using environment variables, but there are cases in code (error handling, summaries, webhooks) where configuration summaries may inadvertently leak sensitive data (e.g., by failing to redact data in summary embeds or logs). This issue has been patched via commit dffe050.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-65957 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65957 is a high-severity vulnerability in Intercore-Productions Core-Bot, published on 25 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-65957 in the wild and no public exploit code.

Affected product: Intercore-Productions Core-Bot. 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-65957/ (Markdown: https://insights.sbomify.com/CVE-2025-65957/index.md)
```

## Sources

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

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