Program Overview
Booking.com runs a bug bounty program on HackerOne. The program has 49 in-scope assets and is managed by HackerOne's triage team.
49
In-Scope Assets
1h
Avg Response
93%
Efficiency
49d
Avg Bounty Time
98d
Avg Resolve
In-Scope Assets
| Asset | Type | Max Severity | Eligible |
|---|---|---|---|
| *.booking.com | WILDCARD | Critical | Bounty |
| *.fareharbor.com | WILDCARD | Critical | Bounty |
| *.fareharbor.engineering | WILDCARD | Critical | Bounty |
| *.rentalcars.com | WILDCARD | Critical | Bounty |
| accommodations.booking.com | URL | Critical | Bounty |
| account.booking.com | URL | Critical | Bounty |
| admin.booking.com | URL | Critical | Bounty |
| autocomplete.booking.com | URL | Critical | Bounty |
| booking.com | URL | Critical | Bounty |
| careers.booking.com | URL | Critical | Bounty |
| cars.booking.com | URL | Critical | Bounty |
| chat.booking.com | URL | Critical | Bounty |
| compass.fareharbor.com | URL | Critical | Bounty |
| demo.fareharbor.com | URL | Critical | Bounty |
| distribution-xml.booking.com | URL | Critical | Bounty |
| experiences.booking.com | URL | Critical | Bounty |
| fareharborsites.com | URL | Critical | Bounty |
| fhdn.fareharbor.com | URL | Critical | Bounty |
| flights.booking.com | URL | Critical | Bounty |
| http://secure-iphone-xml.booking.com/json/ | URL | Critical | Bounty |
| https://apps.apple.com/us/app/booking-com-hotels-travel/id367003839 | APPLE_STORE_APP_ID | Critical | Bounty |
| https://apps.apple.com/us/app/pulse-for-booking-com-partners/id992795726 | APPLE_STORE_APP_ID | Critical | Bounty |
| https://iphone-xml.booking.com/json/ | URL | Critical | Bounty |
| https://play.google.com/store/apps/details?id=com.booking&hl=en | GOOGLE_PLAY_APP_ID | Critical | Bounty |
| https://play.google.com/store/apps/details?id=com.booking.hotelmanager&hl=en | GOOGLE_PLAY_APP_ID | Critical | Bounty |
| https://secure-iphone-xml.booking.com/json/ | URL | Critical | Bounty |
| indicative-pricing.taxi.booking.com | URL | Critical | Bounty |
| kyc-onboarding.booking.com | URL | Critical | Bounty |
| marketing.fareharbor.com | URL | Critical | Bounty |
| metasearch-api.booking.com | URL | Critical | Bounty |
| paybridge.booking.com | URL | Critical | Bounty |
| paymentcomponent.booking.com | URL | Critical | Bounty |
| paynotifications.booking.com | URL | Critical | Bounty |
| phone-validation.taxi.booking.com | URL | Critical | Bounty |
| portal.taxi.booking.com | URL | Critical | Bounty |
| readonly.fareharbor.com | URL | Critical | Bounty |
| secure-supply-xml.booking.com | URL | Critical | Bounty |
| secure.booking.com | URL | Critical | Bounty |
| sites.fareharbor.com | URL | Critical | Bounty |
| spark.fareharbor.com | URL | Critical | Bounty |
| supplier.auth.toag.booking.com | URL | Critical | Bounty |
| supply-xml.booking.com | URL | Critical | Bounty |
| tableau.fareharbor.engineering | URL | Critical | Bounty |
| taxi.booking.com | URL | Critical | Bounty |
| taxis.booking.com | URL | Critical | Bounty |
| teleport.fareharbor.engineering | URL | Critical | Bounty |
| webhooks.booking.com | URL | Critical | Bounty |
| widget.rentalcars.com | URL | Critical | Bounty |
| www.fareharbor.com | URL | Critical | Bounty |
Out-of-Scope Assets
- ams.merchandise.booking.com
- awscpasslab.booking.com
- business.booking.com/
- cpass.booking.com
- desk-demo-api.fareharbor.engineering
- desk-demo.fareharbor.engineering
- https://fareharbor.com/demo/
- https://secure.booking.com/companyjoin.html
- https://secure.booking.com/enterprise/signon.en-gb.html
- https://ugcupload.booking.com/upload_bbtool_company_logo
- https://www.booking.com/bbm.html
- jobs.booking.com
- medialibrary.booking.com
- partnerfeedback.booking.com
- procurement.booking.com
- recruitmentsurveys.booking.com
- secure.booking.com/company/*
- secure.booking.com/orgnode/*
- spadmin.booking.com/
- surveys.booking.com
Tips for Hacking Booking.com
- Read the policy — Understand what's in scope, out of scope, and any specific testing restrictions before you start.
- Enumerate the attack surface — Use subdomain enumeration and directory bruteforcing to map all accessible endpoints.
- Focus on high-impact bugs — Look for SQL injection, SSRF, and IDOR vulnerabilities first.
- Test authentication flows — Check for OAuth misconfigurations and CSRF in login/signup flows.
- Write clear reports — Include steps to reproduce, impact assessment, and suggested remediation. Use Burp Suite to capture evidence.
Frequently Asked Questions
How do I start hacking Booking.com?
Sign up on HackerOne, read the program policy carefully, review the in-scope assets listed above, and start testing. Always stay within scope and follow responsible disclosure guidelines.
Does Booking.com pay bounties?
Yes, Booking.com offers monetary rewards for valid security vulnerabilities.
What types of vulnerabilities does Booking.com accept?
Booking.com accepts reports for vulnerabilities found in their 49 in-scope assets. Common accepted vulnerability types include XSS, SQL injection, SSRF, IDOR, authentication bypass, and RCE. Check the program policy for specific exclusions.