CVE-2025-62378
MEDIUMDescription
CommandKit is the discord.js meta-framework for building Discord bots. In versions 1.2.0-rc.1 through 1.2.0-rc.11, a logic flaw exists in the message command handler that affects how the commandName property is exposed to both middleware functions and command execution contexts when handling command aliases. When a message command is invoked using an alias, the ctx.commandName value reflects the alias rather than the canonical command name. This occurs in both middleware functions and within the command's own run function. Although not explicitly documented, CommandKit's examples and guidance around middleware usage implicitly convey that ctx.commandName represents the canonical command identifier. Middleware examples in the documentation consistently use ctx.commandName to reference the command being executed. Developers who assume ctx.commandName is canonical may introduce unintended behavior when relying on it for logic such as permission checks, rate limiting, or audit logging. This could allow unauthorized command execution or inaccurate access control decisions. Slash commands and context menu commands are not affected. This issue has been patched in version 1.2.0-rc.12, where ctx.commandName now consistently returns the actual canonical command name regardless of the alias used to invoke it.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 5% of all known CVEs.
References
Related Vulnerabilities
Other CWE-706 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-24813 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2020-15505 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2021-40539 | Critical | 9.8 | 99% | KEV + Ransom | Fix |
| CVE-2024-27292 | High | 7.5 | 69% | - | Fix |
| CVE-2021-40856 | High | 7.5 | 50% | - | - |
| CVE-2021-24122 | Medium | 5.9 | 23% | - | Fix |
Common questions
How do I fix CVE-2025-62378?
No published fix for CVE-2025-62378 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-62378 being actively exploited?
Not that we know of. CVE-2025-62378 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.15% is the estimated probability that it will be exploited in the next 30 days. That is higher than 5% of all scored CVEs.
How severe is CVE-2025-62378?
CVE-2025-62378 has a CVSS v3 base score of 6.1, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-62378
Markdown
[](https://tridentstack.com/cve/CVE-2025-62378)HTML
<a href="https://tridentstack.com/cve/CVE-2025-62378"><img src="https://tridentstack.com/cve/badge/CVE-2025-62378.svg" alt="CVE-2025-62378"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2025-10-16.