Mcp Api
Monthly
Command injection in MissionSquad mcp-api through version 1.11.8 enables remote authenticated users to execute arbitrary OS-level commands on the host by supplying a crafted version string to the NPM package installation endpoint. The root cause is string interpolation of unvalidated user input into a Node.js `exec()` call, which passes the resulting string through a shell interpreter - making shell metacharacters in the version parameter an effective injection vector. Proof-of-concept exploit code exists (CVSS 4.0 E:P); no active exploitation has been confirmed by CISA KEV. A patched release (v1.11.9) is available.
Server-side request forgery in MissionSquad mcp-api up to version 1.11.9 allows authenticated remote attackers to coerce the server into issuing HTTP requests to arbitrary internal or external destinations via unsanitized OAuth Dynamic Client Registration (DCR) endpoint URLs. The vulnerability exists in the `registrationEndpoint` field of OAuth templates processed by `src/services/dcrClients.ts`, which was passed directly to `fetch()` without scheme validation or SSRF filtering. No public exploit identified at time of analysis, though the CVSS 4.0 supplemental E:P flag indicates proof-of-concept evidence exists. A vendor-released patch is available in v1.11.10.
Command injection in MissionSquad mcp-api through version 1.11.8 enables remote authenticated users to execute arbitrary OS-level commands on the host by supplying a crafted version string to the NPM package installation endpoint. The root cause is string interpolation of unvalidated user input into a Node.js `exec()` call, which passes the resulting string through a shell interpreter - making shell metacharacters in the version parameter an effective injection vector. Proof-of-concept exploit code exists (CVSS 4.0 E:P); no active exploitation has been confirmed by CISA KEV. A patched release (v1.11.9) is available.
Server-side request forgery in MissionSquad mcp-api up to version 1.11.9 allows authenticated remote attackers to coerce the server into issuing HTTP requests to arbitrary internal or external destinations via unsanitized OAuth Dynamic Client Registration (DCR) endpoint URLs. The vulnerability exists in the `registrationEndpoint` field of OAuth templates processed by `src/services/dcrClients.ts`, which was passed directly to `fetch()` without scheme validation or SSRF filtering. No public exploit identified at time of analysis, though the CVSS 4.0 supplemental E:P flag indicates proof-of-concept evidence exists. A vendor-released patch is available in v1.11.10.