Threat database

CVE-2026-115453 is an authorization bypass vulnerability in the MarcosCamara01 Ecommerce Template affecting the cart and wishlist repositories. It allows any authenticated user to delete or modify cart and wishlist entries of other users due to improper enforcement of PostgreSQL row level security (RLS). The application connects as the table owner, bypassing RLS policies that rely on user ID checks. Sequential identifiers enable enumeration of other users' cart and wishlist items, leading to unauthorized data modification or deletion.

CVE-2026-115450 is a vulnerability in the MarcosCamara01 Ecommerce Template that allows an authenticated user without special privileges to manipulate the checkout process. The flaw arises because the cart API accepts separate parameters for the product variant and the Stripe price ID without verifying their consistency. This enables an attacker to pay the price of one product while ordering a different, potentially more expensive product. The vulnerability allows repeated exploitation to purchase goods at the price of the cheapest item in the catalogue, causing order records to mismatch the actual payment amount.

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.