Cross user deletion and modification of cart and wishlist rows in Ecommerce Template through unscoped primary key queries

Overview

Authorization Bypass Through User-Controlled Key (CWE-639) in the cart and wishlist repositories of MarcosCamara01 Ecommerce Template allows any authenticated user to delete and modify the cart and wishlist rows of any other user, because cartRepository.delete(), cartRepository.updateQuantityInternal() and wishlistRepository.delete() in src/lib/db/drizzle/repositories/ match rows by primary key alone, with no predicate on the owning user, and the per user authorization for those three operations rests on PostgreSQL row level security. The migrations run ALTER TABLE ... ENABLE ROW LEVEL SECURITY and create policies comparing app.current_user_id() with user_id, but never ALTER TABLE ... FORCE ROW LEVEL SECURITY, and PostgreSQL does not apply policies to the role that owns a table. The template uses one DATABASE_URL both to run the migrations, which create the tables, and for the application at runtime, so the application connects as the owner of the tables and the policies do not apply to it. cart_items.id and wishlist.id are sequential bigserial values, so the identifiers of rows belonging to other users can be enumerated, and the update path returns the modified row, which carries the identifier of the user it belongs to. This results in the destruction and modification of cart and wishlist contents belonging to other accounts of the installation.

Affected

• ecommerce_template >= b139a11c7bfab82b9c54c738b9a5d6015b439972 < adf7dedbb41894c0bad0b33a26999b0da7e967b7

Remediation

Update to a revision of the repository that includes commit adf7dedbb41894c0bad0b33a26999b0da7e967b7 of 27 July 2026. The repository publishes no versioned releases and carries no git tags, so the fix can only be identified by commit.