CVE-2025-62645
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Restaurant Brands International (RBI) assistant platform through 2025-09-06 allows a remote authenticated attacker to obtain a token with administrative privileges for the entire platform via the createToken GraphQL mutation.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe RBI assistant platform contains a broken access control vulnerability in the GraphQL API where the createToken mutation lacks proper authorization checks, allowing any authenticated user to generate administrative tokens and gain full platform access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2025-09-06CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify RBI Assistant platform installationLocate the RBI Assistant platform installation directory or container image and confirm the product name matches 'Rbi Restaurant Brands International Assistant'Affected if The product is installed and is the RBI Assistant platform
-
Check GraphQL API endpoint accessibilityLocate the GraphQL API endpoint configuration (typically /graphql or /api/graphql in the application) and verify the endpoint is exposed and accessibleAffected if The GraphQL API endpoint is reachable without additional network restrictions
-
Verify createToken mutation presenceQuery the GraphQL introspection endpoint to confirm the createToken mutation exists in the schemaAffected if The createToken mutation is defined in the GraphQL schema
-
Test createToken authorizationUsing a low-privilege authenticated user account, attempt to call the createToken mutation with administrative role parameters and observe if the mutation succeeds without authorization errorsAffected if The mutation accepts the request and returns a token without enforcing role-based access control
-
Inspect RBAC configurationReview the application configuration or source code for role-based access control rules on the createToken mutation, looking for missing role validation before token creationAffected if No role validation or insufficient validation is found for the createToken operation
A user is affected if the RBI Assistant platform is running with the GraphQL API accessible and the createToken mutation can be invoked by any authenticated user without proper admin role verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict the createToken GraphQL mutation to only permit authorized administrator roles and implement role-based access control validation before token issuance.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62645 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data