CVE-2025-62378VulnerabilityPublished 15 Oct 2025

CVE-2025-62378: underctrl-io commandkit · Use of Incorrectly-Resolved Name or Reference

Affects underctrl-io commandkitSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium · fixed in 1.2.0 : update underctrl-io commandkit when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.0

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubunderctrl-io/commandkit`pkg:github/underctrl-io/commandkit`Other threats	Affected =1.2.0-rc.1 =1.2.0-rc.2 =1.2.0-rc.3 =1.2.0-rc.4 =1.2.0-rc.5 =1.2.0-rc.6 =1.2.0-rc.7 =1.2.0-rc.8 =1.2.0-rc.9 =1.2.0-rc.10 =1.2.0-rc.11	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade all affected CommandKit instances to version 1.2.0-rc.12 or later, where the issue is fixed. Until upgrading, developers should audit middleware and command logic that depend on ctx.commandName to verify whether they assume it is canonical and adjust logic to explicitly resolve the canonical command name if possible. Implement additional validation in middleware to cross-check command aliases against a whitelist or mapping to canonical names before enforcing permissions or rate limits. Enhance logging to capture both alias and canonical command names to detect suspicious alias usage. Restrict bot command access to trusted users and channels to limit exposure. Employ runtime monitoring to detect anomalous command invocation patterns. Finally, review bot design to minimize reliance on ctx.commandName for security-critical decisions or supplement it with explicit canonical name resolution mechanisms.

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.

Impact

For European organizations deploying Discord bots using affected versions of CommandKit, this vulnerability can lead to unauthorized command execution or bypass of intended access controls. Bots often manage community moderation, user permissions, or automate sensitive operations; thus, incorrect command name resolution can cause middleware to misapply permission checks or rate limits. This may result in privilege escalation within the bot's operational context, unauthorized data access, or manipulation of bot behavior. Although the attack vector is local (an attacker must send commands to the bot), many organizations use Discord bots for internal or community management, increasing exposure. The integrity of bot operations is at risk, potentially undermining trust in automated moderation or logging. Confidentiality impact is limited but present if commands expose sensitive information. Availability is not impacted. The medium severity suggests a moderate risk, but the impact can be significant in environments where bots enforce critical policies or handle sensitive data. European organizations relying on CommandKit for Discord bot development should prioritize patching to prevent misuse and maintain operational security.

CWE-706Use of Incorrectly-Resolved Name or Reference (opens in a new tab)
Class weaknessOWASP Top 10 A01:2021: Broken Access Control (opens in a new tab)
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
Attack patterns
Redirect Access to Libraries (opens in a new tab)
Create files with the same name as files protected with a higher classification (opens in a new tab)
Passing Local Filenames to Functions That Expect a URL (opens in a new tab)
DLL Side-Loading (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/underctrl-io/commandkit/security/advisories/GHSA-fhwm-pc6r-4h2f (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 15 Oct 2025, 17:11 UTC

WeaknessesCWE-706

Technical details

References

Community reviews

Related threats