CVE-2025-62650: Rbi Restaurant Brands International Assistant vulnerability (CVSS 8.3)

Description

The Restaurant Brands International (RBI) assistant platform through 2025-09-06 relies on client-side authentication for use of the diagnostic screen.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeChanged

ConfidentialityLow

IntegrityLow

AvailabilityLow

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

Affected products

Rbi Restaurant Brands International Assistant≤ 2025-09-06

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://archive.today/fMYQpThird Party Advisory
https://bobdahacker.com/blog/rbi-hacked-drive-thrus/Permissions Required
https://web.archive.org/web/20250906134240/https:/bobdahacker.com/blog/rbi-hacked-drive-thrusNot Applicable
https://www.malwarebytes.com/blog/news/2025/09/popeyes-tim-hortons-burger-king-platforms-have-catastrophic-vulnerabilities-say-hackersPress/Media CoverageThird Party Advisory
https://www.yahoo.com/news/articles/burger-king-hacked-attackers-impressed-124154038.htmlPress/Media CoverageThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2025-62650 being actively exploited?

CVE-2025-62650 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.50%.

How severe is CVE-2025-62650?

CVE-2025-62650 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 0.50% probability of exploitation.

Which products are affected by CVE-2025-62650?

Affected products include Rbi Restaurant Brands International Assistant.

How do I fix CVE-2025-62650?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2025-62650 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo