<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Budibase - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/budibase/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Thu, 21 May 2026 11:34:07 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/budibase/feed.xml" rel="self" type="application/rss+xml"/><item><title>Budibase Multiple Vulnerabilities</title><link>https://feed.craftedsignal.io/briefs/2026-05-budibase-multiple-vulnerabilities/</link><pubDate>Thu, 21 May 2026 11:34:07 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-budibase-multiple-vulnerabilities/</guid><description>Multiple vulnerabilities in Budibase could be exploited by an attacker to gain administrative privileges, bypass security measures, perform cross-site scripting attacks, manipulate data, or disclose confidential information.</description><content:encoded><![CDATA[<p>Multiple vulnerabilities have been identified within Budibase that could allow an attacker to perform various malicious activities. These include gaining administrative privileges, circumventing existing security measures, executing Cross-Site Scripting (XSS) attacks, manipulating sensitive data, and disclosing confidential information. The specifics of the vulnerabilities, such as CVE IDs or detailed technical descriptions, are not provided in the source document, making it difficult to assess the exact attack vectors and impact without further information. However, the potential for privilege escalation, data manipulation, and XSS attacks makes this a critical issue for organizations utilizing Budibase.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a vulnerable Budibase instance accessible over the network.</li>
<li>Attacker exploits a vulnerability (e.g., authentication bypass) to gain unauthorized access.</li>
<li>Attacker leverages gained privileges to escalate to administrator level.</li>
<li>Attacker bypasses security controls to inject malicious code or scripts.</li>
<li>Attacker executes Cross-Site Scripting (XSS) attacks to compromise user sessions.</li>
<li>Attacker manipulates data within the Budibase application, potentially altering critical business information.</li>
<li>Attacker exfiltrates sensitive or confidential information accessible through Budibase.</li>
<li>Attacker maintains persistent access for future malicious activities.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of these vulnerabilities could lead to a range of adverse outcomes, including unauthorized access to sensitive data, modification of critical business information, and compromise of user accounts. The extent of the impact would depend on the specific vulnerabilities exploited and the scope of data and functionality accessible through the Budibase application. Without further details, it is challenging to estimate the precise number of potential victims or affected sectors.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the generic XSS detection rule to identify potential cross-site scripting attacks against Budibase applications.</li>
<li>Monitor Budibase logs (if available) for suspicious activity, and investigate any anomalies related to authentication or authorization.</li>
<li>Implement the generic privilege escalation detection rule to catch attempts to gain admin privileges.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>privilege-escalation</category><category>defense-evasion</category><category>execution</category><category>impact</category><category>discovery</category><category>cloud</category></item><item><title>Budibase Security Bypass Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-budibase-security-bypass/</link><pubDate>Mon, 18 May 2026 10:34:53 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-budibase-security-bypass/</guid><description>An authenticated remote attacker can exploit a vulnerability in Budibase to bypass security measures and manipulate data.</description><content:encoded><![CDATA[<p>A security vulnerability exists within Budibase that could allow an authenticated remote attacker to bypass security precautions and manipulate data. The vulnerability's specifics are not detailed in this brief but the core issue leads to unauthorized data manipulation within the Budibase application. Defenders should apply any patches as soon as possible, and investigate any unexpected data modifications.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker authenticates to the Budibase application with valid credentials.</li>
<li>The attacker leverages an unspecified vulnerability to bypass access controls.</li>
<li>The attacker crafts a malicious request to access restricted data.</li>
<li>The vulnerable component processes the request without proper authorization checks.</li>
<li>The attacker modifies sensitive data within the Budibase application.</li>
<li>The attacker validates successful data manipulation through the Budibase user interface or API.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to bypass intended security controls and manipulate sensitive data within the Budibase application. This could lead to data corruption, unauthorized disclosure of confidential information, or disruption of business processes that rely on the integrity of the data stored within Budibase.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the latest security patches and updates provided by Budibase to remediate the security bypass vulnerability.</li>
<li>Monitor Budibase application logs for suspicious activity, particularly related to data modification requests.</li>
<li>Implement strict access control policies within Budibase and regularly review user permissions.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>security-bypass</category><category>data-manipulation</category></item><item><title>Budibase REST Datasource SSRF via HTTP Redirect Bypass (CVE-2026-45715)</title><link>https://feed.craftedsignal.io/briefs/2026-05-budibase-ssrf/</link><pubDate>Fri, 15 May 2026 17:54:56 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-budibase-ssrf/</guid><description>Budibase is vulnerable to server-side request forgery (SSRF) via HTTP redirects in the REST datasource integration, allowing authenticated Builders to bypass IP blacklists and access internal services.</description><content:encoded><![CDATA[<p>Budibase is susceptible to a server-side request forgery (SSRF) vulnerability within its REST datasource integration. This flaw allows an authenticated &quot;Builder&quot; user to bypass the built-in IP blacklist and access internal network resources. The vulnerability stems from the <code>_req()</code> method in <code>packages/server/src/integrations/rest.ts</code> not re-checking the IP blacklist after an HTTP redirect, an oversight previously addressed in the automation steps (<code>fetchWithBlacklist</code> in <code>packages/server/src/automations/steps/utils.ts</code>). By setting up an attacker-controlled server to redirect requests to internal services or cloud metadata endpoints, an attacker can steal sensitive information. This issue was confirmed on Budibase v3.34.6, with a fix released in version 3.38.1. This poses a significant risk to cloud environments where Budibase instances are deployed, as it can lead to credential theft and unauthorized access to internal resources.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker sets up a redirect server (e.g., using Python's <code>http.server</code>) on a publicly accessible IP address, configured to redirect to an internal service or cloud metadata endpoint.</li>
<li>An authenticated &quot;Builder&quot; user in Budibase creates a REST datasource, configuring it to point to the attacker's redirect server.</li>
<li>The Builder initiates a query using the newly created REST datasource. The request includes the attacker's server URL in the <code>path</code> field of the query configuration.</li>
<li>Budibase's <code>_req()</code> method in <code>packages/server/src/integrations/rest.ts</code> performs an initial IP blacklist check on the attacker's server URL. Because the attacker's server is public, this check passes.</li>
<li>The <code>fetch()</code> function follows the HTTP redirect (301/302/307) to the internal target specified by the attacker's server (e.g., <code>http://169.254.169.254/latest/meta-data/iam/security-credentials/</code>). Critically, this redirect is NOT re-checked against the IP blacklist.</li>
<li>The request is sent to the internal target, bypassing the intended security control.</li>
<li>The internal target (e.g., cloud metadata service) responds with sensitive information.</li>
<li>Budibase receives the response from the internal target and displays it to the Builder user, effectively leaking sensitive information like cloud IAM credentials or allowing access to internal services.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The vulnerability allows attackers to bypass the IP blacklist and access internal services, leading to potential data breaches. On cloud instances, attackers can steal IAM credentials from metadata endpoints like <code>169.254.169.254</code>. Successful exploitation enables access to internal services such as CouchDB (<code>:4005</code>), Redis (<code>:6379</code>), and MinIO (<code>:4004</code>). This SSRF vulnerability was previously fixed in automation steps (commits <code>6cfa3bcca3</code>, <code>e7d47625be</code>) but not in the REST datasource integration, highlighting a critical oversight.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Budibase to version 3.38.1 or later to patch CVE-2026-45715.</li>
<li>Deploy the Sigma rule &quot;Detect Budibase SSRF via REST Datasource to Metadata Endpoint&quot; to detect exploitation attempts targeting cloud metadata endpoints.</li>
<li>Deploy the Sigma rule &quot;Detect Budibase SSRF via REST Datasource Redirect&quot; to detect exploitation attempts redirecting to internal services.</li>
<li>Review and audit existing REST datasource configurations for any suspicious URLs that may point to external or unexpected internal targets.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>ssrf</category><category>budibase</category><category>cve-2026-45715</category></item></channel></rss>