Applebee’s fixes app flaw that exposed customer data, researcher says

Applebee’s fixes app flaw that exposed customer data, researcher says

Lead Applebee’s, the U.S. restaurant chain owned by Dine Brands, confirmed on Thursday that it has patched a security flaw in its Android app that could have allowed anyone to retrieve personal information of its registered customers. The vulnerability was uncovered earlier this month by U.K.–based security researcher Robert Wiggins of What Security, who found a hard‑coded database password embedded in the app’s source code. According to TechCrunch, the flaw gave unrestricted access to a database containing names, email addresses, birth dates, phone numbers, ZIP codes and other details.

Discovery of the flaw Robert Wiggins, a veteran cybersecurity researcher, used artificial‑intelligence tools to scan thousands of lines of decompiled code from Applebee’s Android application, which has amassed more than a million downloads on Google Play. As reported by TechCrunch, his search revealed a credential that granted direct entry to the company’s customer database. Hard‑coding passwords in software is widely recognized as a severe security lapse because the secret can be extracted by anyone who can download and reverse‑engineer the app.

Scope of exposed data TechCrunch verified Wiggins’s findings by independently downloading and decompiling the Android app, confirming the presence of the exposed credential. The outlet also created a test Applebee’s account with dummy data, which allowed the researcher to query the database and retrieve the stored information. According to the report, the database contained customers’ full names, email addresses (including verification status), dates of birth, phone numbers, ZIP codes, veteran status, login counts, account creation dates, and the IP addresses of recent log‑ins—data points that can be used to approximate a user’s location.

Company response and investigation Applebee’s disclosed that its security team launched an investigation as soon as the issue was brought to its attention. As reported by TechCrunch, a Dine Brands spokesperson said the company had “promptly launched an investigation and has not currently found any evidence of unauthorized access.” The spokesperson declined to confirm whether server logs exist that could reveal past access attempts, and did not specify how long the hard‑coded password had been present in the app. The company also refrained from estimating how many of its roughly 8.5 million rewards‑program members might have been affected, noting that determining the exact number would require the AI model to access potentially every record—a step the researcher deemed unnecessary.

Reporting challenges Wiggins indicated that Applebee’s and its parent company, Dine Brands, lack a public mechanism for receiving vulnerability disclosures. Consequently, the researcher approached TechCrunch for assistance in notifying the company. Based on reports, the lack of a formal reporting channel may have delayed remediation, although the flaw was ultimately patched before the story’s publication.

Regulatory considerations TechCrunch queried whether Applebee’s would inform customers or file a disclosure with the U.S. Securities and Exchange Commission, as required for material cybersecurity incidents involving publicly traded firms. The company did not respond to those inquiries, leaving the regulatory status of the incident unclear.

Brief analysis Opinion: The Applebee’s episode underscores the persistent risk of hard‑coded credentials in consumer‑facing applications. While the swift patch suggests an effective internal response once the issue was identified, the absence of a clear vulnerability‑reporting pathway may have prolonged exposure. Companies handling large volumes of personal data should adopt secure credential‑management practices and establish transparent channels for security researchers to report findings.

Conclusion The Applebee’s case illustrates how a single overlooked credential can jeopardize the privacy of millions of customers. According to TechCrunch, the flaw has been remedied, but the incident raises broader questions about security hygiene and disclosure processes within large restaurant chains and their parent corporations. Ongoing monitoring and transparent communication will be essential to restore consumer confidence and to prevent similar oversights in the future.

Source: TechCrunch

Frequently Asked Questions

How was the Applebee’s database password discovered?

Security researcher Robert Wiggins used AI‑assisted analysis of the decompiled Android app code to locate a hard‑coded credential that granted access to the customer database, as reported by TechCrunch.

What type of personal information was exposed?

The exposed database contained customer names, email addresses (with verification status), dates of birth, phone numbers, ZIP codes, veteran status, login counts, account creation dates, and recent login IP addresses, according to TechCrunch.

Has Applebee’s confirmed any unauthorized access to the data?

A Dine Brands spokesperson told TechCrunch that the investigation has not found evidence of unauthorized access, though the company did not disclose details about server logs or the duration the password was present in the app.

Source: TechCrunch — Read more

💻 Related Articles