Categories
CVE-2026-90896

Vulnerability in MarcosCamara01 Ecommerce Template (CVE-2026-90896)

Summary

Vulnerability in MarcosCamara01 Ecommerce Template (CVE-2026-90896). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/stripe/checkout_sessions.

Original description

The description as published by the source.

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.

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-90896 has been found in MarcosCamara01 Ecommerce Template.
Attackers can target a specific entry point like GET /api/stripe/checkout_sessions over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "MarcosCamara01 Ecommerce Template CVE-2026-90896" on the vendor's site.

CVE-2026-90896 (MarcosCamara01 Ecommerce Template) — CWE-306
Attack surface: GET /api/stripe/checkout_sessions / POST /api/stripe/payment / Referer header
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-306) exists in MarcosCamara01 Ecommerce Template. Attackers reach the vulnerable code path via GET /api/stripe/checkout_sessions.

📍 Affected scope

Check the vendor advisory for the affected versions of MarcosCamara01 Ecommerce Template. Attack surface: GET /api/stripe/checkout_sessions / POST /api/stripe/payment / Referer header.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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 GET /api/stripe/checkout_sessions requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで MarcosCamara01 Ecommerce Template を使っているサービスとバージョンを洗い出す。

  2. 2
    Hunt for indicators of compromise detect
    grep 'GET /api/stripe/checkout_sessions' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /api/stripe/checkout_sessions への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify
    Replay attack against GET /api/stripe/checkout_sessions on staging to confirm patch closes the vector

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

References

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