Bug bounty reports15,219
Publicly disclosed HackerOne reports, with the platform's own outcome and severity.
| Report | Status | Weakness | Severity | Disclosed | Bounty | Votes |
|---|---|---|---|---|---|---|
| Wordpress Users Disclosure (/wp-json/wp/v2/users/)#1663363 | Valid | Information Disclosure | Medium | 2022-08-11 | – | 6 |
| Disable xmlrpc.php file#712321 | Valid | No weakness recorded | Low | 2022-08-11 | – | 10 |
| able to login into login.topechelon.com#712318 | Valid | Access Control | High | 2020-05-20 | – | 12 |
| xmlrpc.php FILE IS enable it will used for Bruteforce attack and Denial of Service(DoS)#1622867 | Valid | Denial of Service | Medium | 2022-08-08 | – | 14 |
| Public and secret api key leaked in JavaScript source#1051029 | Valid | Access Control | High | 2021-01-19 | – | 21 |
| Clickjacking in main domain https://topechelon.com/Analysed#2964441 | Valid | No weakness recorded | High | 2025-02-10 | – | 80 |
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 (2,190 analysed so far), which can be wrong. Data as of 2026-11-15.