Intel

AIKIDO-2026-406032

better-auth is vulnerable to Improper Authorization

GHSA-g95c-wqvr-8c3jPublished Nov 4, 2026
November 4, 2026

68

CVE Score

Medium

Improper Authorization

Are you affected? Scan for Free

TL;DR

better-auth's admin /admin/update-user endpoint requires a separate user:set-email permission to change a user's email address, but passes the phoneNumber and phoneNumberVerified fields through with only the general user:update permission. A user with a limited role that holds user:update can put their own phone number, marked as verified, on another user's account and then sign in to that account with a phone OTP, taking over the victim's session, including accounts with more privileges than their own. The fix requires a new user:set-phone permission whenever either phone field is present in the request.

How do I fix this?

Upgrade the better-auth library to the patch version. Changing phoneNumber or phoneNumberVerified through update-user now requires the new user:set-phone permission, which the default admin role has. If you use custom access control, add set-phone to your statements and grant it to the roles that should be allowed to change phone numbers.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range, you use both the admin plugin and the phone number plugin, and a role other than the full admin role holds the user:update permission. You are not affected if only full administrators can update users.

Versions

0.0.1 - 1.7.15

Fixed in 1.7.16

Background info

better-auth is vulnerable to Improper Authorization in versions 0.0.1 - 1.7.15.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea