underctrl-io commandkit up to 1.2.0-rc.11 commandName name resolution
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in underctrl-io commandkit up to 1.2.0-rc.11. It has been rated as problematic. Affected by this vulnerability is an unknown functionality. Performing a manipulation of the argument commandName results in name resolution. This vulnerability was named CVE-2025-62378. The attack needs to be approached locally. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability was found in underctrl-io commandkit up to 1.2.0-rc.11. It has been classified as problematic. This affects an unknown function. The manipulation of the argument commandName with an unknown input leads to a name resolution vulnerability. CWE is classifying the issue as CWE-706. 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-62378 since 10/10/2025. The exploitability is told to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 1.2.0-rc.12 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 1.2.0-rc.0
- 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
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Name resolutionCWE: CWE-706
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: commandkit 1.2.0-rc.12
Timeline
10/10/2025 CVE reserved10/15/2025 Advisory disclosed
10/15/2025 VulDB entry created
10/15/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-fhwm-pc6r-4h2f
Status: Confirmed
CVE: CVE-2025-62378 (🔒)
GCVE (CVE): GCVE-0-2025-62378
GCVE (VulDB): GCVE-100-328713
Entry
Created: 10/15/2025 19:33Changes: 10/15/2025 19:33 (65)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.