CVE-2026-72849 budibase CVE debrief

Who should care

Budibase users and administrators should be aware of this vulnerability and take steps to patch or mitigate it. Affected operator, platform, vulnerability-management, and security-team impact should be carefully evaluated to ensure proper remediation and minimize potential damage. Security teams should prioritize patching and implement additional security measures to prevent cross-site request forgery attacks.

Technical summary

Budibase before 3.40.0 contains a cross-site request forgery vulnerability in the chat-link handoff endpoint. Attackers can craft a phishing page that auto-submits a POST request with a leaked confirmation token to bind their chat identity to a victim user's account, enabling impersonation within agent operations and inheritance of victim permissions. This vulnerability allows for potential cross-site request forgery attacks, emphasizing the need for patching or mitigation.

Defensive priority

Budibase users should prioritize patching to prevent potential cross-site request forgery attacks.

Recommended defensive actions

• Patch Budibase to version 3.40.0 or later
• Restrict access to chat-link handoff endpoint
• Monitor for suspicious POST requests with leaked confirmation tokens
• Implement additional security measures to prevent cross-site request forgery attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Budibase before 3.40.0 contains a cross-site request forgery vulnerability in the chat-link handoff endpoint. Evidence is limited; verify Budibase version and chat-link handoff endpoint exposure. Check for external chat identity bindings and leaked confirmation tokens. Limited evidence suggests that attackers can craft a phishing page that auto-submits a POST request with a leaked confirmation token to bind their chat identity to a victim user's account. Further verification is required to confirm affected scope and severity.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.