{"answers":{"affected":"2 open source packages ship an affected version, including commandkit.","exploited":"There is no known exploitation of CVE-2025-62378 in the wild and no public exploit code.","fix":"Upgrade commandkit to 1.2.0-rc.12 or later.","what":"CVE-2025-62378 is a medium-severity vulnerability in underctrl-io commandkit, published on 15 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-62378 and fix it if it is affected.\n\nWhat it is: CVE-2025-62378 is a medium-severity vulnerability in underctrl-io commandkit, published on 15 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-62378 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- commandkit (npm): affected from 1.2.0-rc.1; fixed in 1.2.0-rc.12\n- commandkit (npm): affected from 1.2.0-rc.1; fixed in 1.2.0-rc.12\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62378/ (Markdown: https://insights.sbomify.com/CVE-2025-62378/index.md)","id":"CVE-2025-62378","markdown":"https://insights.sbomify.com/CVE-2025-62378/index.md","name":"CVE-2025-62378","record":{"aliases":["GHSA-fhwm-pc6r-4h2f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Discord bot framework","requires_auth":"low_privilege","summary":"Developers relying on canonical command names for access control may bypass restrictions when aliases are used, potentially allowing unauthorized command execution.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-706","name":"Use of Incorrectly-Resolved Name or Reference"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"CommandKit exposes incorrect command name in context object for message command aliases","id":"CVE-2025-62378","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":2,"n_references":1,"next":{"headline":"Open Redirect in reflex-dev/reflex","id":"CVE-2025-62379"},"packages":[{"ecosystem":"npm","fixed":["1.2.0-rc.12"],"introduced":["1.2.0-rc.1"],"last_affected":[],"package":"commandkit","purl":null,"source":"GHSA-fhwm-pc6r-4h2f"},{"ecosystem":"npm","fixed":["1.2.0-rc.12"],"introduced":["1.2.0-rc.1"],"last_affected":[],"package":"commandkit","purl":"pkg:npm/commandkit","source":"GHSA-fhwm-pc6r-4h2f"}],"prev":{"headline":"pwn.college DOJO vulnerable to improper authentication in workspace endpoint allowing unauthorized Windows VM access","id":"CVE-2025-62376"},"products":["commandkit"],"published":"2025-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-15","vendors":["underctrl-io"]},"summary":"Developers relying on canonical command names for access control may bypass restrictions when aliases are used, potentially allowing unauthorized command execution.","url":"https://insights.sbomify.com/CVE-2025-62378/"}