# CVE-2026-129884: thirdweb Dashboard through commit 940b3745 Missing Authorization via fetchClientSecret Server Action

> Unauthenticated attackers can create Stripe checkout sessions for other teams in thirdweb Dashboard, obtaining their client secrets.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 16 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-87g3-vgh8-32mx

## What is CVE-2026-129884?

CVE-2026-129884 is a medium-severity missing authorization vulnerability in thirdweb Dashboard, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

thirdweb Dashboard through commit 940b3745 contains a missing authorization vulnerability in the fetchClientSecret Next.js server action that allows unauthenticated attackers to create Stripe checkout sessions for other teams. Attackers can invoke the action with a forged Team object containing a victim's stripeCustomerId to obtain Growth plan Checkout session client secrets with attacker-influenced return URLs.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-129884?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-129884?

No fix has been published for CVE-2026-129884 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129884 being exploited?

There is no known exploitation of CVE-2026-129884 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129884 and fix it if it is affected.

What it is: CVE-2026-129884 is a medium-severity missing authorization vulnerability in thirdweb Dashboard, published on 16 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129884 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: thirdweb Dashboard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-129884/ (Markdown: https://insights.sbomify.com/CVE-2026-129884/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-129884
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-129884
- OSV: https://osv.dev/vulnerability/CVE-2026-129884

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-129884/
Summaries are generated and may contain mistakes; the official description above is the record.
