Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Tabnabbing in template comments - stripo.email#759133 | Valid | Misconfiguration and Insecure Design | Low | 2020-01-31 | – | 5 |
| Clickjacking on my.stripo.email for MailChimp credentials#737625 | Informative | Misconfiguration and Insecure Design | Medium | 2020-01-08 | – | 7 |
| No Rate Limiting on /reset-password-request/ endpointAnalysed#764122 | Valid | Misconfiguration and Insecure Design | Medium | 2020-02-04 | – | 14 |
| Password token leak via Host headerAnalysed#737042 | Valid | Misconfiguration and Insecure Design | Medium | 2019-12-19 | – | 20 |
| weak password poilicy in signup password leak to account takeoverAnalysed#985367 | Valid | Misconfiguration and Insecure Design | None | 2020-10-16 | – | 23 |
| Memory Dump and Env Disclosure via Spring Boot ActuatorAnalysed#1019367 | Valid | Misconfiguration and Insecure Design | Medium | 2021-03-02 | – | 27 |
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.