Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| CreatorID leaked from public content posted to SnapMapsAnalysed#867521 | Valid | Server-Side Request Forgery | Medium | 2020-12-18 | $1,000 | 49 |
| Server-Side Request Forgery using Javascript allows to exfill data from Google MetadataAnalysed#530974 | Valid | Server-Side Request Forgery | – | 2020-11-30 | – | 421 |
| Access to multiple production Grafana dashboardsAnalysed#663628 | Valid | Information Disclosure | High | 2020-11-04 | $10,000 | 464 |
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.