FKIE_CVE-2025-62378
Vulnerability from fkie_nvd - Published: 2025-10-15 17:16 - Updated: 2026-10-08 11:10
Severity
Summary
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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "commandkit",
"vendor": "underctrl-io",
"versions": [
{
"status": "affected",
"version": "\u003e= 1.2.0-rc.1 \u003c 1.2.0-rc.12"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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\u0027s own run function. Although not explicitly documented, CommandKit\u0027s 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."
},
{
"lang": "es",
"value": "CommandKit es el meta-framework de discord.js para construir bots de Discord. En las versiones 1.2.0-rc.1 a 1.2.0-rc.11, existe una falla l\u00f3gica en el gestor de comandos de mensajes que afecta c\u00f3mo la propiedad commandName se expone tanto a las funciones middleware como a los contextos de ejecuci\u00f3n de comandos al manejar alias de comandos. Cuando un comando de mensaje es invocado usando un alias, el valor ctx.commandName refleja el alias en lugar del nombre can\u00f3nico del comando. Esto ocurre tanto en las funciones middleware como dentro de la propia funci\u00f3n run del comando. Aunque no est\u00e1 expl\u00edcitamente documentado, los ejemplos y la gu\u00eda de CommandKit sobre el uso de middleware transmiten impl\u00edcitamente que ctx.commandName representa el identificador can\u00f3nico del comando. Los ejemplos de middleware en la documentaci\u00f3n usan consistentemente ctx.commandName para referenciar el comando que se est\u00e1 ejecutando. Los desarrolladores que asumen que ctx.commandName es can\u00f3nico pueden introducir un comportamiento no deseado al depender de \u00e9l para l\u00f3gica como verificaciones de permisos, limitaci\u00f3n de velocidad o registro de auditor\u00eda. Esto podr\u00eda permitir la ejecuci\u00f3n no autorizada de comandos o decisiones imprecisas de control de acceso. Los comandos de barra y los comandos de men\u00fa contextual no se ven afectados. Este problema ha sido parcheado en la versi\u00f3n 1.2.0-rc.12, donde ctx.commandName ahora devuelve consistentemente el nombre can\u00f3nico real del comando, independientemente del alias utilizado para invocarlo."
}
],
"id": "CVE-2025-62378",
"lastModified": "2026-10-08T11:10:00.250",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "NONE",
"baseScore": 6.1,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "HIGH",
"privilegesRequired": "LOW",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 4.2,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-62378",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-10-15T17:13:11.098735Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-10-15T17:16:00.313",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/underctrl-io/commandkit/security/advisories/GHSA-fhwm-pc6r-4h2f"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-706"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…