CVE-2025-62378

Workaround

If upgrading isn't immediately possible:

• Use ctx.command.data.command.name for permission validations, or
• Include all command aliases in your permission logic.

References

• CommandKit repository
• Middleware documentation

A logic flaw exists in the message command handler of CommandKit 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, and the documentation describes middleware as suitable for “logging, authentication, permission checks, or any other cross-cutting concerns.” As a result, developers reasonably expect ctx.commandName to return the canonical command name and may rely on it for security-sensitive logic.

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.

CVE-2025-62378 has a CVSS score of 6.1 (Medium). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.0-rc.12); upgrading removes the vulnerable code path.

Kodem intelligence

Fixed in v1.2.0-rc.12.
ctx.commandName now consistently returns the actual canonical command name, regardless of the alias used to invoke it.

1. What is CVE-2025-62378? CVE-2025-62378 is a medium-severity security vulnerability in commandkit (npm), affecting versions >= 1.2.0-rc.1, <= 1.2.0-rc.11. It is fixed in 1.2.0-rc.12.
2. How severe is CVE-2025-62378? CVE-2025-62378 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of commandkit are affected by CVE-2025-62378? commandkit (npm) versions >= 1.2.0-rc.1, <= 1.2.0-rc.11 is affected.
4. Is there a fix for CVE-2025-62378? Yes. CVE-2025-62378 is fixed in 1.2.0-rc.12. Upgrade to this version or later.
5. Is CVE-2025-62378 exploitable, and should I be worried? Whether CVE-2025-62378 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-62378 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-62378? Upgrade commandkit to 1.2.0-rc.12 or later.