CVE-2026-115453: CWE-639 Authorization Bypass Through User-Controlled Key in MarcosCamara01 Ecommerce Template
Description
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.
CVSS v4.0
Score 7.1high
Affected software
MarcosCamara01
Ecommerce Template
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The MarcosCamara01 Ecommerce Template suffers from an authorization bypass (CWE-639) in its cart and wishlist repositories. The vulnerability arises because the cartRepository.delete(), cartRepository.updateQuantityInternal(), and wishlistRepository.delete() functions match rows solely by primary key without verifying ownership. Although PostgreSQL row level security policies are defined to restrict access based on the current user ID, the application connects to the database using the table owner's role, which is exempt from these policies. Additionally, the absence of FORCE ROW LEVEL SECURITY means policies do not apply to the owner role. Sequential bigserial IDs allow attackers to enumerate other users' cart and wishlist items. Consequently, authenticated users can delete or modify cart and wishlist data belonging to other users within the same installation.
Potential Impact
Authenticated users can bypass intended authorization controls to delete or modify cart and wishlist entries of other users. This compromises data integrity and privacy within the ecommerce application, potentially leading to user disruption and loss of trust. The vulnerability does not require elevated privileges beyond authentication but exploits misconfiguration of database security policies.
Mitigation Recommendations
No official patch or fix is currently documented. Mitigation requires changing the database connection to avoid using the table owner role at runtime, ensuring that PostgreSQL row level security policies are enforced by using FORCE ROW LEVEL SECURITY on affected tables, and verifying that application queries include predicates restricting access to the current user's data. Review and update database roles and policies to prevent owner role bypass. Monitor vendor advisories for official fixes or updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Secur0
- Date Reserved
- 2026-10-22T14:49:43.872Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ada2ff34d27ba8daa632c12
Added to database: 10/22/2026, 15:46:59 UTC
Last enriched: 10/22/2026, 16:00:22 UTC
Last updated: 10/22/2026, 16:02:48 UTC
Views: 6
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.