Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| `use-mcp`'s oauth2 process uses a window.open call with untrusted mcp server provided data allowing for code execution under the page using itAnalysed#3211031 | Valid | Cross-site Scripting | Medium | 2025-09-30 | $550 | 75 |
| [Variation of #3321406] YetAnother 1-Click Chaining of Self-XSS, Cookie Tossing and AntiCSRF Token Prediction leads to auto approval in AccessTempAuthAnalysed#3423950 | Valid | Cross-site Scripting | High | 2026-04-14 | – | 63 |
| AI Playground XSS to steal user-chat messages and access to connected MCP ServerAnalysed#3424998 | Valid | Cross-site Scripting | Low | 2026-02-26 | – | 62 |
| Second-Order XSS via javascript protocol in MCP Server Portal Apps leads to ATOAnalysed#3316910 | Valid | Cross-site Scripting | Low | 2025-12-16 | – | 50 |
Status and severity are HackerOne's. “Access stated” is what the title says; “Access needed” and techniques come from CyberSIXT's analysis of the public report (3,935 analysed so far), which can be wrong. Data as of 2026-11-15.