Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Sat, 21 Nov 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | @better-auth/stripe 1.2.0-beta.18 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5 contains an authorization bypass vulnerability because the stripeCustomerId user field accepts values from sign-up and update-user requests, letting a user replace their own Stripe customer ID with another customer's. Attackers who know another customer's Stripe ID can open that customer's billing portal to view invoices and billing details, change payment methods, and cancel or modify subscriptions. | |
| Title | @better-auth/stripe before 1.7.16 Authorization Bypass via stripeCustomerId Mass Assignment | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-11-21T16:34:51.608Z
Reserved: 2026-11-20T23:52:03.518Z
Link: CVE-2026-134317
No data.
No data.
No data.
OpenCVE Enrichment
No data.
-
CWE-639
Authorization Bypass Through User-Controlled Key