Account takeover via unbound email-change account identifier
Published Aug 12, 2026 · Updated Aug 12, 2026
Authorization bypass in Budibase before 3.40.0 allows remote authenticated users to take over accounts through an email-change request. POST /api/v2/email trusts a body-supplied accountId without requiring it to match the authenticated session, so verification changes the selected victim's email. Exploitation requires a victim account identifier obtained outside the normal cross-user API surface; the attacker then receives a password-reset link and accesses the victim's account.
Summary
What happened
Authorization bypass in Budibase before 3.40.0 allows remote authenticated users to take over accounts through an email-change request. POST /api/v2/email trusts a body-supplied accountId without requiring it to match the authenticated session, so verification changes the selected victim's email. Exploitation requires a victim account identifier obtained outside the normal cross-user API surface; the attacker then receives a password-reset link and accesses the victim's account.
The record
- CVE
- CVE-2026-73303
- Published
- Aug 12, 2026
- Updated
- Aug 12, 2026
- Vendor
- Budibase
- Product
- Budibase
- Classifications
- CWE-639, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 12, 2026CVE publishedPublication date reported by the CVE source.
- Aug 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.40.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory account-takeover reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo