# CVE-2026-115453: Authorization Bypass Through User-Controlled Key (CWE-639) in the cart and wishlist repositories of MarcosCamara01 Ecommerce Template allows


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-j5qr-vh53-fq3q

## What is CVE-2026-115453?

CVE-2026-115453 is a high-severity vulnerability in MarcosCamara01 Ecommerce Template, published on 22 Oct 2026. 

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-115453?


## How do I fix CVE-2026-115453?

No fix has been published for CVE-2026-115453 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-115453 being exploited?

There is no known exploitation of CVE-2026-115453 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115453 and fix it if it is affected.

What it is: CVE-2026-115453 is a high-severity vulnerability in MarcosCamara01 Ecommerce Template, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115453 in the wild and no public exploit code.

Affected product: MarcosCamara01 Ecommerce Template. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115453/ (Markdown: https://insights.sbomify.com/CVE-2026-115453/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115453
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115453
- OSV: https://osv.dev/vulnerability/CVE-2026-115453

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115453/
Summaries are generated and may contain mistakes; the official description above is the record.