Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Host header poisoning leads to account password reset links hijacking#167631 | Not checked yet | Information Disclosure | – | – | – | 43 |
| Email link poisoning / Host header attack#182670 | Not checked yet | No weakness recorded | – | – | $200 | 38 |
| Git available containing passwords.#173811 | Not checked yet | Access Control | – | – | $400 | 24 |
| [www.boozt.com] - Authentication bypass#257305 | Not checked yet | Authentication | – | – | $200 | 23 |
| xss in Theme http://bztfashion.booztx.com#166694 | Not checked yet | Cross-site Scripting | – | – | $250 | 15 |
| Potential Subdomain Takeover Possible#166826 | Not checked yet | No weakness recorded | – | – | $120 | 14 |
| Instance of Apache Vulnerable to Several Issues#166871 | Not checked yet | Denial of Service | – | – | $80 | 12 |
| Users Unable to login using Gmail/Facebook on https://boozt-stage1.booztx.com/login#279932 | Not checked yet | Authentication | – | – | $100 | 9 |
| PHP info page disclosure on http://www.day.dk/#165930 | Not checked yet | Information Disclosure | – | – | $60 | 9 |
| User Enumeration.#165894 | Not checked yet | Information Disclosure | – | – | – | 9 |
| Reflected XSS on www.boozt.com#99594 | Not checked yet | Cross-site Scripting | – | – | $100 | 9 |
| Http header injection#168254 | Not checked yet | Misconfiguration and Insecure Design | – | – | – | 7 |
| booztfashion.com URL should HTTPS#268622 | Not checked yet | No weakness recorded | – | – | – | 6 |
| Weak Password#255668 | Not checked yet | Misconfiguration and Insecure Design | – | – | $60 | 6 |
| XSS#167321 | Not checked yet | Cross-site Scripting | – | – | $120 | 6 |
| Email spoofing at booztlet.com#200748 | Not checked yet | Misconfiguration and Insecure Design | – | – | – | 4 |
| Bruteforce Unlimited number of password attempts#272832 | Not checked yet | Authentication | – | – | – | 3 |
| Password reset token issue#253934 | Not checked yet | Authentication | – | – | $60 | 3 |
| Application code is not obfuscated -- OWASP M9 (2016)#205925 | Not checked yet | Misconfiguration and Insecure Design | – | – | – | 3 |
| Make victim buy in attacker's account without any idea - http://www.booztlet.com/#167731 | Not checked yet | Authentication | – | – | $80 | 3 |
| Bypass email validity in newsletter field#200072 | Not checked yet | Misconfiguration and Insecure Design | – | – | – | 2 |
| Android app does not use SSL for login#166712 | Not checked yet | Cryptography | – | – | – | 2 |
| No Session change on Password change#280585 | Not checked yet | Authentication | – | – | – | 1 |
| ADB Backup is enabled within AndroidManifest#170398 | Not checked yet | Information Disclosure | – | – | – | 1 |
| Broken Authentication and Session Management(Session Fixation)#167698 | Not checked yet | Authentication | – | – | – | 1 |
| No csrf protection on logout#165923 | Not checked yet | Misconfiguration and Insecure Design | – | – | – | 1 |
| No Confirmation During Email Change#280304 | Not checked yet | No weakness recorded | – | – | – | – |
| Cookie Misconfiguration#180397 | Not checked yet | Authentication | – | – | – | – |
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 (549 analysed so far), which can be wrong. Data as of 2026-11-14.