Crazy Bubble Tea IDOR exposes customer data

Published14 January 2026 Vorant ratingroutine vulnerability Retail

Vorant's rating weighs the evidence in the report: confirmed exploitation, victims claimed, CVSS and EPSS, and how many sources agree. It rates the report, not your assets.

CVE-2025-14317 in Crazy Bubble Tea mobile app allowed authenticated attackers to enumerate and access other users' personal information through unvalidated loyaltyGuestId parameter.

Sourcecert.pl — open the original

What to check

Applies to: The 1 CVE named below. Whether you run an affected version is not assessed: check the versions the source lists.
Exploitation: No exploitation in the wild and no public exploit is recorded for the CVEs named.

CERT Polska has disclosed CVE-2025-14317, an insecure direct object reference (IDOR) vulnerability in the Emaintenance Crazy Bubble Tea mobile application. The flaw allows any authenticated user to access personal information of other customers by manipulating the loyaltyGuestId parameter in API requests. The server failed to implement proper authorization checks, enabling attackers to enumerate user IDs and retrieve associated personal data.

The vulnerability has been patched in version 915 for Android and version 7.4.1 for iOS. Organizations using loyalty or point-of-sale applications should review their API authorization controls to ensure user data access is properly restricted to the authenticated session owner.

The issue was responsibly disclosed by security researcher Tobiasz "Palidon" Kostrzewa and coordinated through CERT Polska's vulnerability disclosure program.

Mentioned in this report

Vulnerabilities CVE-2025-14317

Detection guidance

Potential IDOR Enumeration via loyaltyGuestId Parameter Manipulation

ATT&CK T1190 · status experimental · needs webserver logs · generated from the report, not run against telemetry

A behavioural hunt for the technique in general, not a signature for the CVEs this report names.

Detects a single client repeatedly querying a loyalty/POS API endpoint while varying the loyaltyGuestId parameter, indicative of IDOR enumeration to harvest other customers' personal data (as in CVE-2025-14317); correlate over a short time window (e.g. >20 distinct loyaltyGuestId values from one source IP/session within 5 minutes) since Sigma condition syntax here cannot express the count threshold directly. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

title: Potential IDOR Enumeration via loyaltyGuestId Parameter
logsource:
  category: webserver
detection:
  selection:
    cs-uri-stem|contains:
    - /api/
    - /loyalty
    cs-uri-query|contains: loyaltyGuestId=
  filter:
    cs-uri-query|contains:
    - loyaltyGuestId=self
    - loyaltyGuestId={sessionUserId}
  condition: selection and not filter
fields:
- c-ip
- cs-uri-query
- cs-username
- sc-status
falsepositives:
- Customer support or admin tooling that legitimately queries multiple loyalty account
  IDs on behalf of customers
- Automated QA/test suites exercising the loyalty API against many test accounts
level: medium
tags:
- attack.t1190
- attack.collection
id: 440f1e64-3c5d-505f-aa8b-635eb767c4c4
status: experimental
author: Vorant

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://cert.pl/en/posts/2026/01/CVE-2025-14317

Free public brief. The detections with Splunk SPL already written (plus Elastic and KQL where they apply) are in the app with a free account, no card. Slack alerts on the vendors you run come with the paid plans, and a new account gets three days of them.

What this brief leaves out

This page is the free tier: the write-up, the severity, the names. In the app the same report carries its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply) and live profiles of the CVEs it names. The paid plans add the security research and news reporting the free tier leaves out.

It sits in a corpus of 16,566 reports from 147 sources, 722 of them written in the last seven days, and it grows through the day.

A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Slack alerts are a paid-plan feature: name the vendors you run and Slack hears about the reports that touch them, not the rest of the week's. Nothing is charged unless you subscribe.

Create a free account What it costs