All vulnerabilities

Servers and applications

GHSA-pvcr-8mvp-w8qr

Chat-Link Handoff Identity Confusion (Same-Tenant Account-Link CSRF)

Severity
High 7.7
Published
22 Jul 2026
Last changed
22 Jul 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.40.0
Weakness
Improper authorization (CWE-285)Insufficient verification of data authenticity (CWE-345)Cross-site request forgery (CWE-352)
Attack
Over the network · Only under certain conditions · Needs a user account · Needs someone to click or open something
Attacker can
Read data · Change data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
Sources
Project advisories (GitHub)

Description

The Budibase AI chat-link handoff flow (GET/POST /api/chat-links/:instance/:token/handoff) binds an external chat identity (Slack/Discord/MS Teams/Telegram) to a Budibase user account. The confirmation endpoint is on a public route (no CSRF middleware, no auth-group gate) and the only credential it checks is a confirmationToken that is already rendered in plaintext into the HTML confirmation page the victim views. There is no binding between the confirmation token and the requester's Budibase session at preparation time, and no CSRF token on the POST.

Consequently, an attacker who creates a chat-link session for their own external chat identity (or any identity they can mint in their chat platform) can induce a victim Budibase user (same tenant) to submit the confirmation POST -> for example by sending them a link that auto-submits, or by XSS/CSRF on a co-tenanted page -> and the victim's globalUserId becomes bound to the attacker's external identity.

From Budibase/budibase's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
BudibaseServers and applications · github:budibase/budibase
  • Every version before 3.40.0

About Budibase

low-code development platform

From Wikidata, CC0 1.0.
Docker Hub pulls
2,327,272Docker Hub, 15 Nov 2026
GitHub stars
28,419GitHub, 15 Nov 2026
Forks
2,238GitHub, 15 Nov 2026
Latest release
v4.0.0GitHub, 15 Nov 2026
Released
10 Nov 2026GitHub
First published on GitHub
7 Jun 2019GitHub

References