Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Unauthenticated self-registration on ████████ grants full access to internal supplier procurement portal and vendor data#4071064 | Valid | Authentication | Medium | 2026-10-14 | – | 29 |
| Critical SQL Injection WDM API (████████)#3778282 | Valid | SQL Injection | Critical | 2026-08-27 | – | 40 |
| HTML Injection in Contact Form Email Enables Phishing via Legitimate ████████ Infrastructure#3802451 | Valid | Injection and Smuggling | Medium | 2026-10-05 | – | 42 |
| Pre-authentication Stored XSS in Essity Customer-Service Pipeline via ContactApi (reCAPTCHA bypass + no rate limit)#3729501 | Valid | Cross-site Scripting | Critical | 2026-08-27 | – | 48 |
| Unauthenticated API allows reading, writing to and deleting any user's private chat history on ████████#4020767 | Valid | Misconfiguration and Insecure Design | Critical | 2026-09-18 | – | 68 |
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 (779 analysed so far), which can be wrong. Data as of 2026-11-14.