CVE-2026-67329: Authorization Bypass Through User-Controlled Key in better-auth stripe
A vulnerability in @better-auth/stripe versions >=1.4.11 and <1.6.21 allows an authenticated user belonging to multiple organizations to bypass authorization checks when performing subscription-related actions. The issue arises because the middleware validates the organization ID from the query string, but the handler uses the organization ID from the request body or session, leading to inconsistent authorization. This flaw enables unauthorized management of subscription actions and access to billing details of organizations the user should not control.
AI Analysis
Technical Summary
@better-auth/stripe versions >=1.4.11 and <1.6.21 contain an authorization bypass vulnerability in organization subscription actions. The middleware validates the organization ID from the request query string against an authorization callback, but the actual handler reads the organization ID from the request body or falls back to the user's active organization in session. When these IDs differ, an authenticated user who is a member of multiple organizations can perform subscription management actions (such as canceling, changing plans, restoring subscriptions, and accessing the billing portal) on organizations they belong to but should not manage. This also allows unauthorized access to sensitive billing information including payment methods, invoices, and subscription states.
Potential Impact
An authenticated user with membership in multiple organizations can bypass intended authorization controls to manage subscriptions and access billing information of other organizations they belong to but should not have management rights for. This leads to unauthorized subscription modifications and exposure of sensitive billing data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict user permissions to limit membership in multiple organizations or avoid using affected versions. Monitor for vendor updates regarding an official fix.
CVE-2026-67329: Authorization Bypass Through User-Controlled Key in better-auth stripe
Description
A vulnerability in @better-auth/stripe versions >=1.4.11 and <1.6.21 allows an authenticated user belonging to multiple organizations to bypass authorization checks when performing subscription-related actions. The issue arises because the middleware validates the organization ID from the query string, but the handler uses the organization ID from the request body or session, leading to inconsistent authorization. This flaw enables unauthorized management of subscription actions and access to billing details of organizations the user should not control.
CVSS v4.0
Score 7.1high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
@better-auth/stripe versions >=1.4.11 and <1.6.21 contain an authorization bypass vulnerability in organization subscription actions. The middleware validates the organization ID from the request query string against an authorization callback, but the actual handler reads the organization ID from the request body or falls back to the user's active organization in session. When these IDs differ, an authenticated user who is a member of multiple organizations can perform subscription management actions (such as canceling, changing plans, restoring subscriptions, and accessing the billing portal) on organizations they belong to but should not manage. This also allows unauthorized access to sensitive billing information including payment methods, invoices, and subscription states.
Potential Impact
An authenticated user with membership in multiple organizations can bypass intended authorization controls to manage subscriptions and access billing information of other organizations they belong to but should not have management rights for. This leads to unauthorized subscription modifications and exposure of sensitive billing data.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict user permissions to limit membership in multiple organizations or avoid using affected versions. Monitor for vendor updates regarding an official fix.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-29T13:07:47.015Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6deb26bf32cb7a34c1fc21
Added to database: 08/01/2026, 12:48:38 UTC
Last enriched: 08/01/2026, 13:03:41 UTC
Last updated: 08/01/2026, 14:08:41 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.