CVE-2025-62645

9.9 CRITICAL

📋 TL;DR

This vulnerability allows remote authenticated attackers to obtain administrative tokens via a GraphQL mutation in the Restaurant Brands International assistant platform. Attackers can gain full platform control, affecting Burger King, Tim Hortons, and Popeyes systems. Any organization using the vulnerable RBI assistant platform is affected.

💻 Affected Systems

Products:
  • Restaurant Brands International assistant platform
Versions: Through 2025-09-06
Operating Systems: Not specified, likely platform-agnostic
Default Config Vulnerable: ⚠️ Yes
Notes: Affects Burger King, Tim Hortons, and Popeyes restaurant systems using the RBI assistant platform.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete platform takeover allowing attackers to manipulate drive-thru systems, access customer data, disrupt operations, and potentially compromise payment systems across thousands of locations.

🟠

Likely Case

Attackers gain administrative access to manipulate orders, access customer information, disrupt restaurant operations, and potentially deploy ransomware or other malware.

🟢

If Mitigated

With proper network segmentation and monitoring, impact could be limited to isolated systems, but administrative access still poses significant risk.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: CONFIRMED
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit requires authenticated access but is simple to execute via GraphQL mutation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 2025-09-06

Vendor Advisory: Not provided in references

Restart Required: No

Instructions:

1. Contact RBI for updated platform version. 2. Apply security patch. 3. Test in staging environment. 4. Deploy to production. 5. Rotate all administrative tokens.

🔧 Temporary Workarounds

Disable createToken mutation

all

Temporarily disable the vulnerable GraphQL mutation endpoint

Specific commands depend on platform implementation

Implement GraphQL query validation

all

Add strict validation for GraphQL mutations to prevent privilege escalation

Implementation varies by platform

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate the assistant platform
  • Enable detailed logging and monitoring for all GraphQL mutations and token creation events

🔍 How to Verify

Check if Vulnerable:

Test if authenticated users can create administrative tokens via GraphQL createToken mutation

Check Version:

Check platform version against RBI documentation or contact vendor

Verify Fix Applied:

Verify that createToken mutation no longer allows privilege escalation and test with non-admin credentials

📡 Detection & Monitoring

Log Indicators:

  • Unusual token creation events
  • GraphQL createToken mutations from non-admin users
  • Multiple administrative token requests

Network Indicators:

  • GraphQL requests to createToken endpoint
  • Unusual authentication patterns

SIEM Query:

source="graphql_logs" AND mutation="createToken" AND user_role!="admin"

🔗 References

📤 Share & Export