Vulnerability · Published Aug 12, 2026 · Assigned by GitHub_M

CVE-2026-73303Budibase: Email Change IDOR via POST /api/v2/email allows full Account Takeover (accountId not validated against session)

High 8.2

In plain English

A high-severity authorization bypass via user-controlled key in budibase from Budibase. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 24% of all known vulnerabilities).

Severity (CVSS 3.1)8.2High

Exploit odds (30 days)0.3%top 76.2% of all CVEs

Exploited in the wildNo reportsCISA SSVC: none

Attack toolingNoneno public tooling known

Official description

Budibase is an open-source low-code platform. Prior to 3.40.0, POST /api/v2/email on account.budibase.app accepted a client-controlled accountId without binding it to the authenticated session, while checking only currentEmail. An authenticated attacker who obtains a victim account identifier can start the email-change workflow for the victim, receive and submit the verification code through POST /api/v2/email/verification, move the victim email to an attacker-controlled address, and complete a password reset as the victim. This issue is fixed in version 3.40.0.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	@budibase/server	no fix listed	GHSA-c8vc-7pv3-g98p

Affected products (as reported)

Vendor	Product	Versions
Budibase	budibase	< 3.40.0

Weakness: CWE-639 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

References

https://github.com/Budibase/budibase/security/advisories/GHSA-c8vc-7pv3-g98p x_refsource_CONFIRM
https://github.com/Budibase/budibase/releases/tag/3.40.0 x_refsource_MISC