# CVE-2026-90896: Missing authentication in Ecommerce Template checkout session endpoint allows unauthenticated disclosure of buyer PII

> Unauthenticated attackers can retrieve sensitive buyer PII from checkout sessions due to missing access controls in the API endpoint.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/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
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-qfqr-55gf-4v3j

## What is CVE-2026-90896?

CVE-2026-90896 is a high-severity missing authorization vulnerability in MarcosCamara01 Ecommerce Template, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authentication for Critical Function (CWE-306) in the checkout session lookup handler (src/app/api/stripe/checkout_sessions/route.ts), exposed at GET /api/stripe/checkout_sessions, in MarcosCamara01 Ecommerce Template before commit 91e273c allows a remote, unauthenticated attacker holding a valid Stripe Checkout Session id (cs_...) to retrieve the full session object, including the buyer's name, email, phone, billing address, amount paid and internal userId, because the GET handler calls stripe.checkout.sessions.retrieve() and returns the result without checking for an authenticated session or session ownership. Sibling endpoints such as POST /api/stripe/payment already enforced authentication via auth.api.getSession(); this endpoint had no access control whatsoever. The session_id is exposed in the buyer's own browser URL after payment (success_url = /result?session_id={CHECKOUT_SESSION_ID}), so it leaks through Referer headers, analytics tools, server access logs and shared-machine browser history, resulting in disclosure of the buyer's personal data to an unauthenticated actor.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-90896 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90896 is a high-severity missing authorization vulnerability in MarcosCamara01 Ecommerce Template, published on 14 Sep 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-90896 in the wild and no public exploit code.

Affected product: MarcosCamara01 Ecommerce Template. 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-90896/ (Markdown: https://insights.sbomify.com/CVE-2026-90896/index.md)
```

## Sources

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

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