Read more of this story at Slashdot.
Backend
Applebee's Exposed Customers' Personal Data After Leaving Database Password In App
Slashdot0 views
Joe_Dragon shares a report from TechCrunch: Applebee's has fixed a security flaw that allowed anyone to access the personal information of its registered customers, after a researcher found a password for an internal database inside Applebee's mobile app, TechCrunch has learned. The popular restaurant chain confirmed [last Thursday] that it had taken action to address the security issue to prevent any unauthorized access to its customer database. [...] The exposed database contained customer names, email addresses (including whether or not the customer verified their email), dates of birth, phone numbers, and ZIP codes. The data also included veteran status, the number of times customers had logged in, when their accounts were created, and the IP addresses of their most recent log-ins, which can be used to reveal the person's approximate location. [...] When asked by TechCrunch, the spokesperson would not say if the company has server logs that it can review to determine whether anyone accessed the database, or if it has any logs at all. "Our investigation is ongoing, and we will take appropriate steps based on our findings," the company added. It's unclear how many customers were affected by the data exposure. [...] Applebee's had at least 8.5 million customers enrolled in its rewards program as of last year, though the company would not provide a number of how many customers had their personal information exposed by this security flaw.
Source:https://yro.slashdot.org/story/26/11/05/2230215/applebees-exposed-customers-personal-data-after-leaving-database-password-in-app?utm_source=rss1.0mainlinkanon&utm_medium=feedPreviousUbuntu refreshes time zone data for Canadian clock changesNextSources: Thinking Machines Lab is raising $5B led by Accel at a $40B pre-money valuation, more than tripling its valuation from its last public round last year (Business Insider)
Related posts
I built a tree format for LLM code edits. Against a fair baseline, it only wins where structure matters
0dev.to TypeScript
Testing Electron Apps: A Practical Guide to Unit, Integration, and E2E Coverage
0dev.to JavaScript
Spectrelang beats Zig and Rust in performance by up to 6x
0dev.to Go

An AI Testing Presentation Became the Final Push for Organizational Change at My Company
0dev.to AI

Testing an AI Code Reviewer Against Real GitHub Pull Requests
0dev.to AI
How to Configure Claude Code with a Custom API Endpoint
0dev.to AI