Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PR:L for authenticated-only access; S:C because SSRF inherently affects systems beyond the vulnerable component via server-as-proxy.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
4DescriptionCVE.org
A flaw has been found in MissionSquad mcp-api up to 1.11.9. The affected element is an unknown function of the file src/services/dcrClients.ts. Executing a manipulation can lead to server-side request forgery. The attack may be performed from remote. Upgrading to version 1.11.10 is sufficient to fix this issue. This patch is called f068ab4ad6f0907ac7001b995588c2673f11a755. You should upgrade the affected component.
AnalysisAI
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. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires an authenticated session with sufficient privileges to submit or modify OAuth template configurations containing a `registrationEndpoint` field (PR:L per CVSS 4.0 vector). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-assigned CVSS 4.0 score of 2.1 reflects limited per-system impact (VC:L/VI:L/VA:L) and no subsequent-system impact (SC:N/SI:N/SA:N), which appears conservative for an SSRF vulnerability - SSRF canonically enables probing of internal networks that the attacker cannot reach directly, implying at least partial subsequent-system impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade mcp-api to version 1.11.10 (https://github.com/MissionSquad/mcp-api/releases/tag/v1.11.10), which introduces `validateExternalMcpUrl()` and `assertSafeDcrRegistrationEndpoint()` to enforce that `registrationEndpoint` values use only http or https schemes, are well-formed absolute URLs, and do not resolve to loopback or internal addresses before any `fetch()` call is issued. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-53924
GHSA-p5w2-mr8m-c9xj