CVE Catalog

CVE-2026-115453

HighCVSS 7.1
Published: Updated: Translated: NVD NIST

Summary

The cart and wishlist repositories of the MarcosCamara01 Ecommerce Template contain an authorization bypass through user-controlled key (CWE-639). cartRepository.delete(), cartRepository.updateQuantityInternal() and wishlistRepository.delete() match rows by primary key alone with no owner predicate, and per-user authorization relies on PostgreSQL row level security. Migrations enable RLS and create policies, but never FORCE ROW LEVEL SECURITY, and PostgreSQL does not apply policies to the table owner role; the application connects as the owner, so policies do not apply. Identifiers are sequential, so they can be enumerated, allowing any authenticated user to delete and modify other users' carts and wishlists.

Risk Assessment

Any authenticated user can destroy and modify other accounts' cart and wishlist contents. This undermines data integrity and trust in the e-commerce platform.

Recommendation

Apply FORCE ROW LEVEL SECURITY or use a separate non-owner database role for the application. Add explicit owner predicates in repository queries.

Other vulnerabilities in MarcosCamara01 Ecommerce Template

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS