CVE-2026-54351: Budibase Webhook Mass Assignment Vulnerability (CVSS 8.2)
Budibase versions before 3.39.9 contain a vulnerability in their webhook trigger system that allows an authenticated attacker to hijack automations. By crafting a malicious webhook POST request with a specially modified body, an attacker can trick the system into executing an automation under a different application context than intended. This grants the attacker unauthorized access to read and modify data in the victim's workspace database. The flaw stems from the webhook endpoint accepting and passing unvalidated user input directly into automation parameters without proper access controls.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 8.2 HIGH · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
- Weaknesses (CWE)
- CWE-915
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-06-26 / 2026-06-30
NVD description (verbatim)
Budibase is an open-source low-code platform. Prior to 3.39.9, the webhook trigger endpoint in Budibase is publicly accessible and passes the full HTTP request body into automation execution parameters. A mass assignment vulnerability in externalTrigger() allows an attacker to overwrite the internal appId property by including it in the webhook POST body. When the automation is processed asynchronously (the default path for webhooks without a collect step), the worker executes the attacker-defined automation in the context of the victim's workspace, granting full read/write access to the victim's database. This vulnerability is fixed in 3.39.9.
2 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the externalTrigger() function within Budibase's webhook handling mechanism. The endpoint accepts POST requests and passes the entire HTTP request body into automation execution parameters without sanitization. A mass assignment flaw allows an attacker to inject an appId property into the webhook body, overwriting the legitimate application context. When the automation is processed asynchronously (the default behavior for webhooks without a collect step), the worker executes the attacker-controlled automation using the hijacked appId, effectively running the attacker's logic within the victim's workspace authentication context. CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes) describes this class of vulnerability where object properties are modified through unsanitized user input.
Business impact
An attacker with valid authentication credentials can access and modify sensitive data across an entire workspace's database. This includes potential exfiltration of confidential records, unauthorized modification or deletion of business-critical data, and disruption of automated workflows. For organizations using Budibase to manage customer data, internal records, or operational workflows, this vulnerability could expose regulated information and breach compliance obligations. The risk is amplified in multi-tenant deployments where workspace isolation is a core security assumption.
Affected systems
Budibase versions prior to 3.39.9 are vulnerable. The open-source low-code platform is affected across all deployments—whether self-hosted or cloud-based—that run unpatched versions. The vulnerability requires the attacker to already possess valid authentication credentials to craft and send the malicious webhook request, limiting the initial attack surface to internal or trusted users with platform access.
Exploitability
Exploitation requires an authenticated user (PR:L in the CVSS vector) but does not require user interaction. The attack complexity is rated as HIGH, likely due to the need to understand the application's internal appId structure and successfully craft a webhook payload that reaches asynchronous processing. However, once an attacker grasps the mechanics, the exploit is straightforward: send a POST request to a known webhook endpoint with a manipulated body. Public documentation and typical webhook patterns may make this feasible for determined attackers. The vulnerability is not currently listed in the Known Exploited Vulnerabilities (KEV) catalog, though this does not indicate real-world exploitation has not occurred.
Remediation
Organizations must immediately upgrade Budibase to version 3.39.9 or later. The patch address the mass assignment vulnerability by implementing proper input validation and sanitization in the webhook trigger handler, ensuring that user-supplied request bodies cannot overwrite critical internal properties like appId. Review webhook configurations and audit logs for any suspicious webhook activity or unauthorized automation executions prior to patching. Consider temporarily disabling webhooks in sensitive deployments until the patch is applied if forensic investigation is required.
Patch guidance
Upgrade Budibase to version 3.39.9 or later. Consult the official Budibase release notes and security advisories for any breaking changes or migration guidance associated with the patch. For self-hosted instances, verify the upgrade path through the Budibase documentation to ensure minimal disruption. Cloud-hosted customers should confirm patch deployment status with their service provider. After patching, restart all worker processes to ensure the new code is active, as the vulnerability is triggered during asynchronous automation execution.
Detection guidance
Examine webhook logs and automation execution records for anomalous appId values or automations executed under unexpected application contexts. Look for POST requests to webhook endpoints that include appId in the request body—legitimate webhook payloads typically do not contain this parameter. Monitor workspace database access logs for unauthorized read/write operations correlating with webhook triggers. Set up alerts for automation executions initiated via webhooks that target data outside the expected application scope. Forensic analysis may reveal attacker-controlled automation names or actions that differ from intentionally configured workflows.
Why prioritize this
This vulnerability merits immediate attention due to its HIGH CVSS score (8.2) and the severity of the impact: unrestricted read/write access to an entire workspace's database. Although exploitation requires prior authentication, the ability for an insider or compromised account to escalate privileges and exfiltrate or sabotage data makes this a critical control gap. The default asynchronous webhook processing means most configurations are vulnerable by default. The six-day window between publication and the latest modification suggests active vendor engagement, but the lack of KEV listing should not delay organizational response.
Risk score, explained
The CVSS:3.1 score of 8.2 (HIGH) reflects a network-accessible vulnerability with significant impact on confidentiality and integrity. The 'High' complexity factor accounts for the attacker's need to understand internal appId mechanics and craft a valid payload. The 'Low' privilege requirement acknowledges that authentication is necessary, reducing the threat surface compared to unauthenticated vulnerabilities. The 'Changed' scope indicates that the vulnerability affects resources beyond the security scope of the vulnerable component—the attacker gains access to other applications and data within the same workspace. The absence of availability impact (CIA: C=H, I=H, A=N) reflects that the vulnerability enables data access and modification but not denial of service, though data deletion remains a concern under the integrity impact rating.
Frequently asked questions
Do I need authentication to exploit this vulnerability?
Yes. The CVSS vector shows PR:L (Low Privilege), meaning an attacker must already have valid credentials to authenticate to the Budibase platform. However, this could include a low-privilege user account, compromised credentials, or an insider threat. The barrier is authentication, not administrative access.
Does upgrading to 3.39.9 automatically fix past exploitation?
No. The patch prevents future exploitation but does not remediate damage or unauthorized access from prior attacks. After upgrading, conduct a forensic review of workspace access logs, automation history, and database changes during the vulnerability window. Implement additional controls such as database transaction audits and access monitoring to detect any lingering compromise.
Are cloud-hosted Budibase instances automatically protected?
That depends on your cloud provider's patch deployment schedule. Contact your service provider to confirm when version 3.39.9 will be deployed to your instance. Self-hosted deployments are your responsibility to update. Do not assume automatic protection.
What if I cannot upgrade immediately?
Temporarily disable or restrict access to webhook endpoints if operationally feasible. Implement network-level controls to limit who can send requests to webhook URLs. Monitor all webhook activity and automation logs vigilantly. However, these are temporary mitigations—upgrading to 3.39.9 is the proper fix.
This analysis is provided for informational purposes and reflects the vulnerability details published as of June 2026. SEC.co does not warrant the accuracy of vendor patch versions, release notes, or deployment timelines—verify all remediation guidance against the official Budibase security advisory and release channels. Exploit details are intentionally withheld. Organizations must conduct their own risk assessment and testing before deploying patches. Consult your security team and legal counsel regarding compliance obligations related to this vulnerability. Source: NVD (public-domain), retrieved 2026-08-05. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-42863HIGHFlowiseAI Mass Assignment Vulnerability in Chatflow Update Endpoint
- CVE-2026-44494HIGHAxios Prototype Pollution to MITM Gadget Chain (v1.0.0–1.15.x)
- CVE-2026-44495HIGHAxios Prototype Pollution Gadget Vulnerability (0.31.0 & 1.15.1)
- CVE-2026-45687HIGHRocket.Chat File Upload Field Injection (CVSS 8.5)
- CVE-2026-46475HIGHFlowise Mass-Assignment Privilege Escalation (v3.1.2 Patch)
- CVE-2026-46476HIGHFlowise Cross-Workspace Template Takeover Vulnerability
- CVE-2026-46477HIGHFlowise Dataset Cross-Workspace Takeover (CVSS 8.8)
- CVE-2026-46478HIGHFlowise DatasetRow Mass-Assignment Cross-Workspace Takeover (8.8 HIGH)