CyberRota Analysis
AI-GeneratedBudibase versions prior to 3.39.25 are vulnerable to a flaw that allows co-builders to access OAuth2 access and refresh tokens from automation test results due to a lack of user scoping. This could lead to unauthorized access to sensitive user credentials, potentially compromising the security of the application. Organizations using Budibase for development should prioritize upgrading to version 3.39.25 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Budibase is an open-source low-code platform. Prior to 3.39.25, packages/server/src/api/controllers/automation.ts returned automation test results containing trigger.outputs.user.oauth2, broadcast BuilderSocketEvent.AutomationTestProgress to the app room, and stored progress in packages/server/src/automations/testProgress.ts without user scoping. A co-builder could receive or poll another SSO-authenticated builder test and obtain OAuth2 access and refresh tokens. The fix adds sanitizeAutomationTestResult and isolates progress by user. This issue is fixed in version 3.39.25.