# CVE-2026-4547: mickasmt next-saas-stripe-starter Checkout generate-user-stripe.ts generateUserStripe logic error

> Attackers can manipulate priceId in the Stripe checkout handler to bypass business logic, potentially altering subscription costs or entitlements.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-chcq-j338-6wqm

## What is CVE-2026-4547?

CVE-2026-4547 is a medium-severity vulnerability in mickasmt next-saas-stripe-starter, published on 22 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in mickasmt next-saas-stripe-starter 1.0.0. Affected is the function generateUserStripe of the file actions/generate-user-stripe.ts of the component Checkout Handler. The manipulation of the argument priceId leads to business logic errors. The attack may be initiated remotely.

Weakness: CWE-840

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


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

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

## Is CVE-2026-4547 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4547 is a medium-severity vulnerability in mickasmt next-saas-stripe-starter, published on 22 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4547 in the wild and no public exploit code.

Affected product: mickasmt next-saas-stripe-starter. 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-4547/ (Markdown: https://insights.sbomify.com/CVE-2026-4547/index.md)
```

## Sources

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

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