Budibase

Unauthorized S3 signed-URL generation in Budibase prior to 3.41.3 allows any authenticated published-app user holding the low-privilege BASIC role to supply arbitrary bucket and key values to POST /api/attachments/:datasourceId/url and receive valid signedUrl and publicUrl values generated using the application's stored S3 datasource credentials. The root cause is missing authorization (CWE-862) on this endpoint, which fails to restrict low-privileged app users from invoking datasource-credential-backed operations. No public exploit or CISA KEV listing has been identified at time of analysis, though the low attack complexity and the wide availability of BASIC-role accounts in published Budibase apps makes this a realistic internal threat.

SSRF via DNS rebinding in Budibase's REST datasource integration (versions prior to 3.40.0) lets an authenticated builder or tenant bypass the outbound-fetch IP blacklist by exploiting a TOCTOU gap between hostname validation and undici's independent DNS re-resolution at connection time. Because the REST integration overrides the transport with undici's fetch, the validated Node.js agent pin established by the prior CVE-2026-54353 fix is silently ignored, leaving the single most-used outbound path in Budibase unprotected. An attacker who can configure a REST datasource can reach cloud instance-metadata endpoints to steal IAM credentials, or read from and write to internal services such as CouchDB, Redis, and MinIO with full HTTP method and response access. No public exploit has been identified at time of analysis.

SQL injection in Budibase's PostgreSQL datasource connector allows an authenticated administrator to execute arbitrary DDL and DML statements against the connected PostgreSQL database by supplying a crafted schema name containing embedded double quotes. The vulnerable code in packages/server/src/integrations/postgres.ts interpolates the schema field directly into a SET search_path statement using the simple query protocol, which permits semicolon-delimited multi-statement execution. Impact includes full database read and write access - including extraction of pg_shadow password hashes and potential OS-level file reads via pg_read_file(). No public exploit or CISA KEV listing identified at time of analysis; however, the GHSA advisory provides a complete, step-by-step reproduction procedure making this trivially reproducible. Fixed in version 3.39.19.

Filesystem existence and readability probing in Budibase Cloud's MongoDB integration prior to version 3.40.1 exposes an information-disclosure oracle exploitable by authenticated builders. The `tlsCertificateKeyFile` and `tlsCAFile` fields in the MongoDB datasource configuration were passed unsanitized to the MongoDB driver as server-side filesystem paths, enabling a builder to probe arbitrary absolute paths on the shared multi-tenant server via `/api/datasources/verify` by comparing distinct driver error messages. No CISA KEV listing exists, but the GHSA advisory contains a fully working reproduction command; the vulnerability is specific to Budibase Cloud and does not affect self-hosted deployments.

Credential disclosure in the Budibase low-code platform (versions prior to 3.40.1) lets an unauthenticated attacker steal a REST datasource's stored Bearer, Basic, or static-header secrets. Because RestIntegration._req in packages/server/src/integrations/rest.ts attaches getAuthHeaders and defaultHeaders before resolving the request host, a PUBLIC-role query invoked via POST /api/v2/queries/:queryId can be pointed at an attacker-controlled host - using an absolute URL or a {{ parameter }} in the path - and the API-masked (--secret-value--) credentials are delivered in cleartext. Publicly available exploit code exists (full PoC in the GHSA advisory); no public evidence of active exploitation. This is a bypass of the earlier GHSA-3gp5 fix, which closed the base-URL rewrite vector but added no same-origin check.

Unauthenticated user enumeration and metadata disclosure in Budibase prior to 3.39.32 exposes tenant identifiers, email addresses, user IDs, SSO identifiers, and document revision metadata via a public API endpoint that was intentionally exempted from authentication middleware - accompanied by a `TODO` comment in source acknowledging it should have been restricted. Any network-reachable unauthenticated caller can query the Worker service endpoint `GET /api/global/users/tenant/:id` with an email or user identifier and receive a full `PlatformUser` document. No public exploit code has been identified at time of analysis, though the attack is trivially reproducible from the public GitHub security advisory alone.

OAuth2 access and refresh token theft in Budibase's automation testing pipeline exposes SSO-authenticated builder credentials to any co-builder of the same application, in all versions prior to 3.39.25. When an SSO-authenticated user runs an automation test in the Budibase builder, the full trigger outputs - including the user's OAuth2 access and refresh tokens - are broadcast without sanitization via WebSocket to every builder connected to the same application room, and are simultaneously stored in a server-side in-memory cache accessible to any co-builder via the test status polling endpoint. A vendor-released patch is available in version 3.39.25; no active exploitation has been confirmed and no public proof-of-concept has been identified at time of analysis.

Server-Side Request Forgery in Budibase's AI table generation pipeline (versions prior to 3.39.4) allows a builder-level user to coerce the server into fetching arbitrary internal network endpoints - including cloud metadata services such as 169.254.169.254 - by crafting LLM prompts that cause the AI to output internal IP addresses as attachment column values. The vulnerable code path, `uploadUrl()` in `fileUtils.ts`, uses a bare `node-fetch` call with no SSRF blacklist validation, while sibling code paths in the same codebase correctly use `fetchWithBlacklist()`. No public exploit has been identified at time of analysis and the vulnerability is not listed in CISA KEV; a vendor-released patch is available in version 3.39.4.

Account enumeration and targeted denial-of-service in Budibase prior to 3.39.25 stem from an observable response discrepancy in the login lockout mechanism: the login endpoint returns distinct HTTP 403 headers (X-Account-Locked: 1, Retry-After: 900) for locked existing accounts but a generic 403 for non-existent addresses, allowing an unauthenticated remote attacker to verify whether any email is registered in a tenant. Beyond reconnaissance, an attacker can deliberately trigger 5 failed attempts against a known valid address to lock that account for 900 seconds. No public exploit code has been identified and the vulnerability is not listed in CISA KEV; remediation via upgrade to 3.39.25 is straightforward.

Full account takeover is possible in Budibase's account portal via an Insecure Direct Object Reference (IDOR) in the email-change API endpoint, affecting all versions prior to 3.40.0. POST /api/v2/email on account.budibase.app accepts a client-supplied accountId without binding it to the authenticated session - an authenticated attacker who obtains a victim's accountId UUID can redirect the email-change verification code to an attacker-controlled address, then complete a password reset to seize the victim's account entirely without any victim interaction required. No public exploit code has been identified at time of analysis; the vulnerability is fixed in Budibase 3.40.0.

Missing RBAC middleware on Budibase's GET /api/global/groups API endpoint allows any authenticated BASIC-role user to enumerate all tenant groups, role-to-application mappings, member user lists, builder permission flags, and default-group designations that should be restricted to builders and administrators. All Budibase versions prior to 3.39.25 are affected across both self-hosted and cloud deployments. No active exploitation is confirmed in CISA KEV, but a complete proof-of-concept with Docker-based reproduction steps is publicly disclosed in GitHub Security Advisory GHSA-4qcj-m5wp-jmf4, reducing exploitation effort to near zero for any tenant user with a valid session.

SQL injection in Budibase's MySQL integration (all versions prior to 3.40.0) lets attackers execute arbitrary, stacked SQL statements against connected databases because the MySQL driver is instantiated with multipleStatements: true. Malicious input submitted through Budibase app fields bound to a MySQL datasource is passed to the backend database, enabling full read/write/destroy access. A proof-of-concept is published in the GHSA advisory; there is no public exploit identified as being used in active attacks (not in CISA KEV).

Server-side request forgery in Budibase's REST datasource integration exposes internal cloud infrastructure to authenticated Builder-role users in all versions prior to 3.38.1. The flaw allows a Builder to configure a REST datasource pointing to an attacker-controlled external server, which then responds with an HTTP redirect to a blocked internal IP - the redirect target is never re-validated against the platform's IP blacklist, granting access to cloud metadata endpoints (e.g., AWS IMDSv1 at 169.254.169.254) and other internal services. No public exploit code or active exploitation has been identified at time of analysis, but the technique is well-documented in SSRF research and requires only a Builder account, which is routinely granted in collaborative low-code environments.

Session hijacking via JavaScript-readable authentication cookies in Budibase versions prior to 3.35.10 allows any Cross-Site Scripting (XSS) vulnerability to escalate into full account takeover. The budibase:auth cookie containing the JWT session token is set with httpOnly: false, enabling JavaScript to read it via document.cookie. Combined with confirmed prior XSS vulnerabilities in Budibase (GHSA-gp5x-2v54-v2q5), attackers can exfiltrate session tokens and gain persistent access to victim accounts. The cookie also lacks secure and sameSite flags, exposing tokens over plaintext HTTP. No public exploit identified at time of analysis. EPSS data not available. Patch available in version 3.35.10.

Authentication bypass in Budibase low-code platform (versions prior to 3.35.4) allows remote unauthenticated attackers to access any protected API endpoint by appending a public endpoint path as a query parameter. The vulnerability stems from unanchored regular expressions in authentication middleware that match against the full request URL including query strings, enabling attackers to craft requests like 'POST /api/global/users/search?x=/api/system/status' to bypass all authentication checks. CVSS score of 9.1 (Critical) reflects network-based remote exploitation with no authentication or user interaction required, resulting in high confidentiality impact and high availability impact. No public exploit code or active exploitation has been identified at time of analysis.

Stored cross-site scripting (XSS) in Budibase's Builder Command Palette (versions prior to 3.32.5) enables authenticated Builder users to inject malicious HTML payloads via entity names (tables, views, queries, automations), achieving session hijacking and account takeover when other Builder-role users invoke the Command Palette. CVSS 8.7 with changed scope reflects the cross-user attack vector. No public exploit identified at time of analysis, though the attack technique is straightforward for authenticated insiders. EPSS data unavailable; patch available in version 3.32.5.

Remote code execution in Budibase versions prior to 3.33.4 allows unauthenticated attackers to execute arbitrary Bash commands with root privileges inside the application container by exploiting public webhook endpoints that trigger automation workflows. The vulnerability stems from improper neutralization of special elements in OS commands (CWE-78) and requires no authentication, though the CVSS complexity is rated high (AC:H). A vendor-released patch is available in version 3.33.4, with the fix publicly documented in GitHub pull request #18238 and commit f0c731b4.

Path traversal in Budibase plugin upload endpoint allows Global Builders to delete arbitrary directories and write files to any accessible filesystem path. Affecting all versions prior to 3.33.4, attackers with high privileges (Global Builder role) can exploit unsanitized filename handling in POST /api/plugin/upload to execute directory traversal attacks remotely with low complexity. CVSS 8.7 (High) with scope change indicates potential container escape or cross-tenant impact. No public exploit identified at time of analysis, though the attack vector is straightforward given the documented path traversal mechanism.

Server-Side Request Forgery (SSRF) in Budibase's REST datasource connector (versions prior to 3.33.4) allows authenticated users with low privileges to bypass IP blacklist protections and access internal network resources. The vulnerability stems from a configuration flaw where the BLACKLIST_IPS environment variable is not set by default in official deployments, causing all blacklist checks to fail silently. With CVSS 9.6 (Critical) due to scope change and high confidentiality/integrity impact, this represents a significant risk for organizations using Budibase in cloud or containerized environments. No active exploitation confirmed (not in CISA KEV), but publicly available exploit code exists via the patch disclosure.

Remote code execution in Budibase low-code platform versions prior to 3.33.4 enables authenticated attackers to execute arbitrary system commands through the bash automation step feature. The vulnerability stems from unsanitized user input processed via template interpolation in execSync calls, allowing command injection with low attack complexity. No public exploit identified at time of analysis, though the technical details disclosed in the GitHub Security Advisory provide a clear exploitation path for authenticated users with automation privileges.

Email flooding denial of service in Budibase prior to version 3.23.25 allows unauthenticated remote attackers to overwhelm user inboxes by repeatedly triggering password reset requests without rate limiting, CAPTCHA, or abuse prevention controls. An attacker can send hundreds of password reset emails to a target address in a short time window, causing user harassment, inbox denial of service, and potential reputational damage. This vulnerability has been patched in version 3.23.25.

Authorization bypass in Budibase 3.31.4 and earlier. The authorized() middleware can be bypassed, enabling injection attacks. PoC available.

Path traversal in Budibase low-code platform 3.31.5 and earlier allows attackers to read arbitrary files through the application builder.

Arbitrary file upload in Budibase 3.24.0 and earlier allows authenticated attackers to bypass UI-level file extension restrictions and upload malicious files by directly manipulating requests. An attacker with valid credentials can circumvent the intended upload controls to potentially execute arbitrary code or compromise system integrity. No patch is currently available for this vulnerability.

Budibase suffers from missing server-side role validation in user management APIs, allowing Creator-level users to escalate privileges and perform unauthorized actions reserved for Tenant Admins and Owners. An authenticated attacker with Creator permissions can promote themselves to Tenant Admin, demote existing administrators, modify owner accounts, and manipulate organizational orders, resulting in complete tenant compromise. No patch is currently available for this high-severity vulnerability.

Command injection in Budibase 3.23.22 and earlier allows authenticated attackers with high privileges to execute arbitrary system commands by injecting malicious values into PostgreSQL connection parameters that are unsanitized in shell command construction. An attacker with administrative access can exploit this vulnerability to gain complete control over the underlying server hosting the Budibase instance. No patch is currently available for this vulnerability.

Unauthorized data access in Budibase low-code platform before 3.30.4 allows unauthenticated users to manipulate internal state. PoC and patch available.

Budibase is a low code platform for creating internal tools, workflows, and admin panels. [CVSS 8.8 HIGH]

Budibase is a low code platform for creating internal tools, workflows, and admin panels. Rated medium severity (CVSS 6.5), this vulnerability is remotely exploitable, low attack complexity. This Server-Side Request Forgery (SSRF) vulnerability could allow attackers to make the server perform requests to unintended internal or external resources.

Improper Control of Dynamically-Managed Code Resources in GitHub repository budibase/budibase prior to 1.3.20. Rated medium severity (CVSS 5.7), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.