Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-67329 high CVSS 7.1

Vulnerability in @better-auth/stripe (CVE-2026-67329)

Summary

Vulnerability in @better-auth/stripe (CVE-2026-67329). Data can be tampered with by attackers. Exploitable via authorizeReference. Mitigation: upgrade to 1.7.0-beta.10 or later.

Original description

The description as published by the source.

Am I affected?

You are affected if all of these are true:

  • You use @better-auth/stripe from version 1.4.11 up to a patched version below. This covers the stable line through 1.6.20 and every 1.7.0 beta through 1.7.0-beta.9.
  • The Stripe plugin has subscriptions turned on (subscription.enabled: true).
  • Organization subscriptions are turned on (organization.enabled: true) and you have set an authorizeReference callback.
  • A user can join more than one org. So a user can be a member of an org whose billing they should not manage.

You are not affected if you only use user subscriptions. You are also not affected if org subscriptions are turned off.

Summary

An org subscription action can run against the wrong org. The actions are cancel, change plan, restore, and open the billing portal. The plugin checks permission against the org id in the request query string. It then runs the action against the caller's active org from their session. When these two ids differ, a member can act on billing for an org they may not manage. The target is always an org the caller belongs to.

Details

The plugin runs two steps for each org subscription action. First, a middleware decides if the caller may use the requested org. It reads the org id from the request body or the query string. It then passes that id to your authorizeReference callback. Second, the route handler runs the action. The handler reads the org id from the request body only. It falls back to the act…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-67329 has been found in @better-auth/stripe.
Attackers can target a specific entry point like authorizeReference over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @better-auth/stripe to 1.7.0-beta.10 or later.
If unsure, ask your IT team or search "@better-auth/stripe CVE-2026-67329" on the vendor's site.

CVE-2026-67329 (@better-auth/stripe) — CWE-639 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: authorizeReference / false
Patched: 1.7.0-beta.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-639) exists in @better-auth/stripe. Attackers reach the vulnerable code path via authorizeReference.

📍 Affected scope

Check the vendor advisory for the affected versions of @better-auth/stripe. Attack surface: authorizeReference / false.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.7.0-beta.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@better-auth/stripe' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@better-auth/stripe' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @better-auth/stripe を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @better-auth/stripe to 1.7.0-beta.10

    ステージング環境で 1.7.0-beta.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @better-auth/stripe
[{"type":"SEMVER","events":[{"introduced":"1.7.0-beta.0"},{"fixed":"1.7.0-beta.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details