Skip to content

Bug bounty reports15,219

Publicly disclosed HackerOne reports, with the platform's own outcome and severity.

Program
Status
Severity
Weakness
Year
Bounty paid0
Access stated
  • No account0
  • A user account0
  • Admin or privileged0
Access needed
Technique:Exposed debug or admin endpoint
Clear filters6 of 15,219 reports
Disclosed bug bounty reports
ReportStatusProgramWeaknessSeverityDisclosedBountyVotes
Django Debug Mode Enabled - Information Disclosure on api.wwm-dev.autodesk.comAnalysed#2965143ValidAutodeskInformation DisclosureMedium2025-03-18–82
PHP info page disclosure in ██████████Analysed#1848780ValidMTN GroupNo weakness recordedMedium2024-08-30–62
Information disclosure due to debug mode enabled at Laravel instance https://mpos.mtn.co.sz/Analysed#2765259ValidMTN GroupInformation DisclosureMedium2025-02-23–61
Information disclosure via enabled Django Debug ModeAnalysed#2201370ValidMTN GroupInformation DisclosureMedium2024-12-25–55
phpinfo() exposed on ██████████Analysed#2641211ValidMarsMisconfiguration and Insecure DesignMedium2024-11-21–51
Sensitive Information DisclosureAnalysed#963352ValidDropcontactInformation DisclosureCritical2020-08-21–47

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.