Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| [Swiftype] - Stored XSS via document field `url` triggers on `https://app.swiftype.com/engines/<engine>/document_types/<type>/documents/<id>`#1245787 | Valid | Cross-site Scripting | High | 2021-08-03 | – | 7 |
| Improper authorization on `/api/as/v1/credentials/` allows any App Search user to access all API keys and escalate privilegesAnalysed#1168528 | Valid | Access Control | High | 2021-06-02 | – | 13 |
| Improper authorization on `/api/as/v1/credentials/` for Dev Role User with Limited Engine AccessAnalysed#1218680 | Valid | Access Control | High | 2021-08-03 | – | 21 |
| Synthetics Recorder: Code injection when recording website with malicious contentAnalysed#1636382 | Valid | Command and Code Injection | High | 2023-04-08 | – | 47 |
| Prototype Pollution leads to XSS on https://blog.swiftype.com/#__proto__[asd]=alert(document.domain)Analysed#998398 | Valid | Cross-site Scripting | High | 2021-08-16 | – | 157 |
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, where there is one, which can be wrong. Data as of 2026-11-15.