What is the CVSS score of CVE-2025-62649?

CVE-2025-62649 has a CVSS 3.1 base score of 5.8 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N. EPSS exploitation probability: 0.5%.

Is there a public PoC exploit available for CVE-2025-62649?

Yes, a public proof-of-concept exploit is available for CVE-2025-62649. Prioritise patching immediately. EPSS: 0.5%.

RBI Assistant Platform CVE-2025-62649

MEDIUM

Use of Client-Side Authentication (CWE-603)

2025-10-17 cve@mitre.org

Information Disclosure Restaurant Brands International Assistant

5.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.8 MEDIUM

AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

vuln.today AI

5.8 MEDIUM

Authorization is enforced only client-side, so a remote attacker needs no privileges (PR:N) or interaction; forged requests affect the backend ordering component (S:C) with low integrity impact and no C/A loss.

3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Oct 08, 2026 - 23:00 vuln.today

CVE Published

Oct 17, 2025 - 21:15 nvd

MEDIUM 5.8

DescriptionNVD

The Restaurant Brands International (RBI) assistant platform through 2025-09-06 relies on client-side authentication for submission of equipment orders.

AnalysisAI

The Restaurant Brands International (RBI) assistant platform, in all versions through 2025-09-06, performs authorization for equipment-order submission only in client-side code, so remote attackers can reach the order-submission endpoint and submit or alter equipment orders without authenticating. Publicly available exploit code exists and the flaw was publicized in September 2025 by security researchers and covered by Malwarebytes and Yahoo News, but it is not listed in CISA KEV, so there is no confirmation of active exploitation; EPSS is 0.51% (42nd percentile), indicating low predicted near-term exploitation. Impact is constrained to integrity of the ordering workflow - the CVSS vector (PR:N, UI:N, S:C, C:N/I:L/A:N) shows no confidentiality or availability loss - and the realistic attack surface is limited to RBI's own hosted deployments rather than broadly deployed third-party software.

Technical ContextAI

The root cause is CWE-603 (Use of Client-Side Authentication): the platform's trust boundary is drawn in the wrong place, with the client - rather than the server/API - deciding whether a user is permitted to submit an equipment order. Because the submitted request itself is trusted, any network-reachable instance of the assistant platform accepts crafted order submissions without a server-side authorization decision, which is why the vector carries AV:N/AC:L/PR:N/UI:N and a Scope Change (S:C) flag: the vulnerable client-side component's failure degrades the security of the server-side ordering system, a different security authority. The assessed vector matches the independent assessment exactly (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N, 5.8), confirming the weakness is exploitable by an unauthenticated remote attacker with no user interaction and no non-default configuration. CPE data (cpe:2.3:a:rbi:restaurant_brands_international_assistant:*:*:*:*:*:*:*:*) marks the entire RBI assistant product line as affected up through the 2025-09-06 cutoff, meaning the design flaw is present by default in any reachable instance rather than being gated behind a feature toggle. One data-quality note: the reference tags classify this as 'Information Disclosure', yet the CVSS vector assigns no confidentiality impact (C:N) and only a low integrity impact (I:L), suggesting the tagging is imprecise and the practical consequence is unauthorized order manipulation rather than data leakage.

RemediationAI

No vendor-released patch was identified at the time of analysis, and the CVE description's 'through 2025-09-06' framing indicates the affected design persisted at least to that date; affected operators should treat the ordering endpoint as untrusted and apply compensating controls. The primary control is architectural: move the authorization decision for equipment-order submission from the client to the server/API so every submission is validated against a server-side session and role check, which is the only durable fix for CWE-603 (trade-off: legacy client integrations that assumed client-side gating may need to be reworked and could break until updated). Until that ships, restrict network access to the order-submission endpoint to known franchisee/operator IP ranges or to an authenticated VPN or zero-trust gateway (trade-off: blocks legitimate ordering from unexpected networks and adds operational friction for field staff), require and validate authenticated sessions with server-issued tokens for submission (trade-off: requires identity plumbing that may not exist), and add rate limiting, anomaly detection, and alerting on order-submission volume and payload patterns to detect abuse (trade-off: detection only, does not prevent the first malicious submission). Given that publicly available exploit code exists, monitor vendor and security-press channels referenced above (Malwarebytes, the researcher write-up, and RBI advisories) for a patched release and deploy it promptly when available.