Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-121802 – Account Takeover / Origin Validation Error – @better-auth/expo (Better Auth) befor

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

Summary

CVE-2026-121802 is a critical origin validation error (CWE-346) in the @better-auth/expo plugin for Better Auth. The plugin signs a caller-supplied state value without checking that the server issued it. An unauthenticated remote attacker can use this to take over accounts, for example by changing the email address of any account. The CVSS v3.1 base score is 9.1 (Critical).

Technical details

  • Root cause: The expo() plugin’s authorization proxy endpoint (/expo-authorization-proxy) signs a user-supplied value without verifying that the server issued it. It signs with the same application secret used for email verification and session cookies.
  • Trigger conditions: The server registers the expo() plugin. Some outcomes, such as wildcard origin matching, also require trustedOrigins to contain wildcard entries like myapp://*.
  • Attack vector: Network, with no privileges and no user interaction required.
  • Impact:
    • An attacker who knows a user’s email address can impersonate that account and change its email address.
    • With session cookie caching enabled, knowing a user’s ID is enough for account takeover.
    • The flaw also allows open redirects to external HTTPS sites and lets misconfigured wildcard origins match unintended URLs.

Affected software

  • @better-auth/expo from 1.4.0-beta.6 up to, but not including, 1.7.16
  • @better-auth/expo from 1.8.0-beta.0 up to, but not including, 1.8.0-beta.5

The CVE record lists the affected range as 0 through 1.7.15. The vendor advisory narrows it to the ranges above.

Severity

CVSS v3.1 base score: 9.1 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade @better-auth/expo to 1.7.16 (1.7.x line) or 1.8.0-beta.5 (1.8 beta line).
  • After upgrading: Rotate the application secret. This invalidates signatures and cookies that were forged before the patch.
  • Workarounds if you cannot patch immediately:
    • Remove the expo() plugin if you don’t need Expo social sign-in.
    • Block requests to /expo-authorization-proxy where the state parameter is not exactly 32 characters of letters, digits, hyphens or underscores.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge