Bug bounty program
TO
TomTom
Most upvoted reports8
| Report | Weakness | Disclosed | Bounty | Votes |
|---|---|---|---|---|
| Exposed Git Repo at http://betaforum.tomtom.com/.git/{subfolders}#541349 | Information Disclosure | – | – | 38 |
| Anonymous user login to Nexus Repository Manager#540698 | Access Control | – | – | 24 |
| Listing of Amazon S3 Bucket accessible to any amazon authenticated user (vector-maps-e457472599)#631529 | Information Disclosure | – | – | 21 |
| Apache mod_status /server-status Information Disclosure#541347 | Information Disclosure | – | – | 9 |
| XSS Reflect#583561 | Cross-site Scripting | – | – | 7 |
| Reflected Cross Site Scripting vuln in tomtom.com#540428 | Cross-site Scripting | – | – | 4 |
| Reflected XSS on www.tomtom.com#557389 | Cross-site Scripting | – | – | 3 |
| CSRF allows attacker to manage customer's shopping cart.#540382 | Cross-Site Request Forgery | – | – | 1 |
Subdomains40,876
| Name | Scope | First seen |
|---|---|---|
| mail-eu.teleatlas.commail | Not in the scope | 2026-11-14 |
| mail-na.teleatlas.commail | Not in the scope | 2026-11-14 |
| autodiscover.tomtom.commail | In scope | 2026-11-14 |
| smtp201.business.tomtom.commail | In scope | 2026-11-14 |
| smtp202.business.tomtom.commail | In scope | 2026-11-14 |
| smtp301.business.tomtom.commail | In scope | 2026-11-14 |
| smtp302.business.tomtom.commail | In scope | 2026-11-14 |
| mail.cn.tomtom.commail | In scope | 2026-11-14 |
| mail.tomtom.commail | In scope | 2026-11-14 |
| mail1.tomtom.commail | In scope | 2026-11-14 |
| mail2.tomtom.commail | In scope | 2026-11-14 |
| mail3.tomtom.commail | In scope | 2026-11-14 |
| mail4.tomtom.commail | In scope | 2026-11-14 |
| mail5.tomtom.commail | In scope | 2026-11-14 |
| autodiscover.mailtest.tomtom.commail | In scope | 2026-11-14 |
| mail3725.arcwor302.telematics.tomtom.commail | In scope | 2026-11-14 |
| mail01.live.telematics.tomtom.commail | In scope | 2026-11-14 |
| mail201.telematics.tomtom.commail | In scope | 2026-11-14 |
| mail202.telematics.tomtom.commail | In scope | 2026-11-14 |
| mail301.telematics.tomtom.commail | In scope | 2026-11-14 |
| mail302.telematics.tomtom.commail | In scope | 2026-11-14 |
| smtp201.telematics.tomtom.commail | In scope | 2026-11-14 |
| smtp202.telematics.tomtom.commail | In scope | 2026-11-14 |
| smtp301.telematics.tomtom.commail | In scope | 2026-11-14 |
| smtp302.telematics.tomtom.commail | In scope | 2026-11-14 |
| webmail.tomtom.commail | In scope | 2026-11-14 |
| imap.tomtomgroup.commail | In scope | 2026-11-14 |
| mail.tomtomgroup.commail | In scope | 2026-11-14 |
| smtp.tomtomgroup.commail | In scope | 2026-11-14 |
| webmail.tomtomgroup.commail | In scope | 2026-11-14 |
| webmail-be.tomtomgroup.commail | In scope | 2026-11-14 |
40,800 names are covered by the program's own scope; 49 were first seen this week. Names come from ProjectDiscovery's public Chaos dataset (passive sources: certificate logs, DNS and other public data), matched to the program by its listing and its own domain scope. A name being in a dataset is not permission to test it: only what the program's own scope says is in scope, and its policy decides. CyberSIXT does not resolve, probe or scan these names. Tags come from the name alone. Source: ProjectDiscovery Chaos. Subdomains on the Atlas, or search the subdomains of every program.
A name in a dataset is not permission to test it: the program's own scope and rules decide. Data as of 2026-11-15.