Skip to content
Artwork for Breach Please
Breach Please · Wednesday · 43 min

S0:E71: A Hardcoded Password Let Anyone Into Wyndham's Customer Database

Big news first: Richy is officially joining Breach Please as a permanent co-host, not just filling in. Welcome to the team. On the story side, Jake, Jess, and Richy dig into Wyndham's hardcoded database credential — a password baked into the Android app that handed anyone access to a Salesforce-hosted customer database, JWTs included. We talk through why storing session tokens at all is a red flag, whether outsourcing your build pipeline gets you off the hook (it doesn't), and how a mealy-mouthed PR response can cost you more than the breach itself. Sources: TechCrunch: https://techcrunch.com/2026/11/09/hotel-giant-wyndham-exposed-customer-data-after-app-security-lapse/ This Week in Security (Zack Whittaker's newsletter): https://this.weekinsecurity.com/ join our discord! https://discord.gg/wYJnTpczV

0:00-43:12

transcript

No transcript — this publisher did not publish one.

show notes

Big news first: Richy is officially joining Breach Please as a permanent co-host, not just filling in. Welcome to the team.

On the story side, Jake, Jess, and Richy dig into Wyndham's hardcoded database credential — a password baked into the Android app that handed anyone access to a Salesforce-hosted customer database, JWTs included. We talk through why storing session tokens at all is a red flag, whether outsourcing your build pipeline gets you off the hook (it doesn't), and how a mealy-mouthed PR response can cost you more than the breach itself.

Sources:

TechCrunch: https://techcrunch.com/2026/11/09/hotel-giant-wyndham-exposed-customer-data-after-app-security-lapse/

This Week in Security (Zack Whittaker's newsletter): https://this.weekinsecurity.com/

join our discord! https://discord.gg/wYJnTpczV