# Crazy Bubble Tea IDOR exposes customer data

Published: 2026-01-14 · Severity: medium · Sectors: retail
Canonical: https://vorant.io/reports/ae52acd9-e6cf-50ad-8181-7da2e1c55a5c/crazy-bubble-tea-idor-exposes-customer-data

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

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 (public sample)

### Potential IDOR Enumeration via loyaltyGuestId Parameter Manipulation

ATT&CK: T1190

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.

```yaml
title: Potential IDOR Enumeration via loyaltyGuestId Parameter
logsource:
  category: webserver
  product: web
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

---

This is the free public brief from Vorant Threat Intelligence. When citing, attribute "Vorant" and link https://vorant.io/reports/ae52acd9-e6cf-50ad-8181-7da2e1c55a5c/crazy-bubble-tea-idor-exposes-customer-data.
Full IOC sets, deployable detections, the entity graph, TAXII 2.1 feed and real-time alerts: https://vorant.io/signup