Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65957: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in Intercore-Productions Core-Bot

0
High
VulnerabilityCVE-2025-65957cvecve-2025-65957cwe-200
Published: Tue Nov 25 2025 (11/25/2025, 23:33:09 UTC)
Source: CVE Database V5
Vendor/Project: Intercore-Productions
Product: Core-Bot

Description

CVE-2025-65957 is a high-severity vulnerability in the open-source Core-Bot by Intercore-Productions, used primarily on Maple Hospital Discord servers. The flaw involves inadvertent exposure of sensitive information such as API keys (SUPABASE_API_KEY, TOKEN) through error handling, summaries, or webhook messages that fail to redact confidential data. This exposure could allow unauthorized actors to access critical credentials, potentially compromising bot operations and connected services. The vulnerability affects versions prior to commit dffe050, which introduced patches to prevent data leakage. Exploitation requires some level of user interaction and privileges but can lead to significant confidentiality and integrity impacts. No known exploits are currently reported in the wild. European organizations using Core-Bot or similar Discord bots with sensitive integrations should prioritize updating to the patched version. Mitigation involves applying the patch, auditing logs and summaries for sensitive data leaks, and restricting bot permissions to minimize potential damage.

AI-Powered Analysis

AILast updated: 11/26/2025, 00:39:57 UTC

Technical Analysis

CVE-2025-65957 is a vulnerability classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) found in the Core-Bot, an open-source Discord bot developed by Intercore-Productions and used notably in Maple Hospital servers. The issue arises because, prior to commit dffe050, the bot's handling of API keys such as SUPABASE_API_KEY and TOKEN relied on environment variables, which is a standard practice. However, certain code paths—specifically in error handling routines, summary generation, and webhook message construction—failed to properly redact or mask these sensitive credentials when generating logs or summary embeds. This flaw could inadvertently expose API keys to unauthorized users who have access to these logs or webhook outputs, potentially allowing them to hijack the bot or access connected backend services. The vulnerability has a CVSS 4.0 score of 8.8, indicating high severity, with attack vector being network-based but requiring high attack complexity and partial privileges with user interaction. The scope and impact on confidentiality, integrity, and availability are all high, as leaked credentials can lead to unauthorized access and manipulation of bot functions and data. The issue was patched in commit dffe050, which introduced proper redaction of sensitive information in all relevant outputs. There are no known exploits in the wild as of the publication date, but the risk remains significant for deployments running vulnerable versions. The vulnerability is particularly relevant for organizations relying on Core-Bot for critical Discord server management and integration with backend services via API keys.

Potential Impact

For European organizations, the exposure of API keys through Core-Bot logs or webhook messages can lead to unauthorized access to backend services such as databases or cloud platforms integrated via SUPABASE_API_KEY or similar tokens. This can result in data breaches, unauthorized data modification, or service disruption. Given the bot’s role in managing Discord servers, attackers could manipulate bot commands, disrupt communications, or escalate privileges within the server environment. Healthcare-related organizations, such as those using Maple Hospital servers, face heightened risks due to the sensitivity of patient data and regulatory requirements under GDPR. The compromise of API keys could also facilitate lateral movement within networks if the bot is integrated with other internal systems. Additionally, the public nature of Discord servers means that attackers might exploit exposed information quickly if logs or summaries are accessible to a broad audience. The high CVSS score reflects the potential for significant confidentiality and integrity damage, which could lead to reputational harm, regulatory penalties, and operational downtime.

Mitigation Recommendations

1. Immediately update Core-Bot to the version including commit dffe050 or later to ensure all sensitive information is properly redacted in logs, summaries, and webhook messages. 2. Conduct a thorough audit of existing logs, summaries, and webhook outputs for any previously exposed API keys or sensitive data and revoke or rotate any compromised credentials. 3. Implement strict access controls on Discord server logs and webhook endpoints to limit visibility to trusted administrators only. 4. Restrict the bot’s permissions to the minimum necessary to reduce the impact of potential compromise. 5. Monitor bot activity and server logs for unusual behavior indicative of credential misuse or unauthorized access. 6. Educate development and operations teams on secure handling of environment variables and sensitive data to prevent similar issues in future code. 7. Consider implementing automated scanning tools that detect sensitive data exposure in logs and code repositories. 8. If possible, use short-lived or scoped API tokens to limit the damage if keys are exposed. 9. Engage in regular security reviews and penetration testing focused on bot integrations and third-party components.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-18T16:14:56.693Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69264a57ca41832e1e4ac27f

Added to database: 11/26/2025, 12:31:19 AM

Last enriched: 11/26/2025, 12:39:57 AM

Last updated: 11/26/2025, 1:02:36 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats