MCP Registry vulnerable to stored XSS in catalogue UI via attribute-quote breakout in publisher-controlled `websiteUrl`
CVE-2026-44429 · GHSA-rqv2-m695-f8j4 · published 2026-05-08 · updated 2026-05-15
- Severity
- Medium
- CVSS score
- 5.4
- Chance of exploitation (EPSS)
- 0.17%
- Fixed in
- 1.7.7
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Stored XSS on the official MCP Registry homepage. The malicious entry sits in the public catalogue alongside legitimate ones; any user expanding the entry triggers the payload. Because the page is served on the official registry.modelcontextprotocol.io origin, the injected script can: Read and overwrite localStorage (baseUrl, customUrl), pinning the user's subsequent reads to an attacker-controlled "Custom" base URL. Issue any same-origin or cross-origin XHR (connect-src * is granted). Phish for Registry JWTs by injecting fake auth flows on the trusted origin. The CSP permits inline event-handler attributes.
Upgrade github.com/modelcontextprotocol/registry to 1.7.7 or later.
1. Replace the homegrown escapeHtml with an attribute-safe encoder that also escapes ", ', backtick, and = — the OWASP HTML attribute-encoding rule. 2. Avoid building the href via string templates. Use setAttribute('href', value) instead — setAttribute is not subject to HTML tokenisation, so no breakout is possible. 3. Tighten validateWebsiteURL to reject any URL whose raw bytes contain ", ', , , \t, or \n, or — conservatively — store the canonical re-serialised form (parsedURL.String() percent-encodes such characters in the path). 4. Drop 'unsafe-inline' from script-src after auditing the inline scripts on the page.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| github.com/modelcontextprotocol/registry | Go | < 1.7.7 | 1.7.7 |
- CriticalJupyter Server: Stored XSS in `NbconvertFileHandler` / `NbconvertPostHandler` via missing `sandbox` CSPjupyter-server
- CriticalMalicious website can execute commands on the local system through XSS in the OpenCode web UIopencode-ai
- CriticalFlowise is vulnerable to stored XSS via "View Messages" allows credential theft in FlowiseAI admin panelflowise
- CriticalMLFlow Cross-site Scripting vulnerability leads to client-side Remote Code Executionmlflow
- CriticalCross-site Scripting in MLFlowmlflow
- HighPraisonAI: Prompt Injection Defense Bypassed for HIGH-Level Threatspraisonai
- MediumMCP Registry has an unauthenticated SSRF: HTTP namespace verification dials 6to4 / NAT64 / site-local IPv6 addresses, bypassing private-addrgithub.com/modelcontextprotocol/registry
- MediumMCP Registry has open redirect via protocol-relative path in trailing-slash middlewaregithub.com/modelcontextprotocol/registry
- LowMCP Registry: OCI validator skips ownership check on upstream rate limitsgithub.com/modelcontextprotocol/registry
- LowMCP Registry's GitHub OIDC tokens are replayable across registry deployments due to shared audiencegithub.com/modelcontextprotocol/registry
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.