Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-73407 – Unauthenticated REST Datasource Credential Theft – Budibase < 3.40.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-73407 is a critical improper access control / sensitive information exposure vulnerability in Budibase’s REST datasource integration. The @budibase/server package attaches a REST datasource’s stored credentials (bearer tokens, basic auth, and static headers) to an outgoing request before validating that the resolved destination host matches the configured datasource, allowing an unauthenticated attacker to redirect a query to an attacker-controlled server and exfiltrate those credentials. The issue carries a CVSS score of 9.0 and is remotely exploitable with a single HTTP request.

Technical details

  • Root cause: in packages/server/src/integrations/rest.ts, the REST integration’s getUrl() logic and request-building flow attach stored datasource credentials before determining the final request host, and no check confirms the resolved host matches the datasource’s configured base URL.
  • Trigger condition: a REST query path parameter can be supplied as, or resolved to, an absolute URL pointing to a different host than the datasource, causing credentials to be sent cross-origin.
  • Attack vector: network, no authentication required — exploitable through a REST query that has been published with the PUBLIC role, so a fully unauthenticated attacker can trigger it with one HTTP request.
  • Impact: exposure/exfiltration of REST datasource authentication material (bearer tokens, basic auth credentials, custom headers) to an attacker-controlled host, which can be leveraged to access the credentials’ underlying systems.

Affected software

  • Budibase server (@budibase/server) versions prior to 3.40.1

Severity

  • CVSS v4.0 Base Score: 9.0 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N

Mitigation and recommended actions

  • Immediate: upgrade Budibase to version 3.40.1 or later, which enforces a same-origin check for REST datasource requests before attaching stored credentials.
  • If immediate patching is not possible: review REST queries published with PUBLIC role permissions and restrict or disable public access to REST datasources that use stored credentials, and rotate any credentials configured on internet-exposed REST datasources.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Named response header x-budibase-tenant-id: any value present
  • Page title: Budibase

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge