Skip to content

Bug bounty reports15,219

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

Program:TomTom
Status
Severity
Weakness
Bounty paid0
Access stated
Access needed
  • No account0
  • A user account0
  • A privileged role0
  • Admin0
  • Physical or local access0
  • Not clear from the report0
Clear filters8 of 15,219 reports
Disclosed bug bounty reports
ReportStatusWeaknessSeverityDisclosedBountyVotes
Exposed Git Repo at http://betaforum.tomtom.com/.git/{subfolders}#541349Not checked yetInformation Disclosure–––38
Anonymous user login to Nexus Repository Manager#540698Not checked yetAccess Control–––24
Listing of Amazon S3 Bucket accessible to any amazon authenticated user (vector-maps-e457472599)#631529Not checked yetInformation Disclosure–––21
Apache mod_status /server-status Information Disclosure#541347Not checked yetInformation Disclosure–––9
XSS Reflect#583561Not checked yetCross-site Scripting–––7
Reflected Cross Site Scripting vuln in tomtom.com#540428Not checked yetCross-site Scripting–––4
Reflected XSS on www.tomtom.com#557389Not checked yetCross-site Scripting–––3
CSRF allows attacker to manage customer's shopping cart.#540382Not checked yetCross-Site Request Forgery–––1

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 (227 analysed so far), which can be wrong. Data as of 2026-11-14.

Updated AboutDevelopersSign in