What's worse is that there was basically no reason for this leak to be possible. I mean, it was apparently a list of all people who'd successfully received a pr

What's worse is that there was basically no reason for this leak to be possible. I mean, it was apparently a list of all people who'd successfully received a press pass for E3 2019. The leak was in the form of an Excel spreadsheet with that info hosted on their server. So why was it even there? It's not the database they're using on the site; from what I've read that's a standard WordPress install. And the spreadsheet was unlikely to be needed outside the organisation itself. Hence the ideal thing to do would have to be to somehow tie the WordPress DB into whatever system they were using. If that'd been done, the leak could never have happened in this way. Alas they didn't, and by going with the old 'intern takes database details, puts them in a spreadsheet and shares around a link' method, exposed thousands of people's details online. It's basically a perfect case study for the dangers of ad hoc spreadsheet solutions and sharing 'private' links around to distribute customer info. Either way, I wouldn't be surprised if someone did sue them under GDPR or what not at this point.