# CVE-2026-108691: mall4j through 4.0 Operator Precedence Error Deletes Other Users' Cart Items via /p/shopCart/cleanExpiryProdList

> Authenticated users can delete other customers' cart items for off-shelf products due to an operator precedence error in SQL logic.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-8r5r-2mmr-2vjr

## What is CVE-2026-108691?

CVE-2026-108691 is a medium-severity missing authorization vulnerability in gz-yami mall4j, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

mall4j through 4.0 contains an improper authorization vulnerability that allows authenticated storefront customers to delete other shoppers' cart items through an operator precedence error in the cleanExpiryProdList SQL statement. Attackers can send one DELETE request to /p/shopCart/cleanExpiryProdList to remove every user's cart entries for off-shelf products, which do not return when products are restocked.

Weakness: CWE-783 (Operator Precedence Logic Error)

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


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

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

## Is CVE-2026-108691 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108691 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108691 is a medium-severity missing authorization vulnerability in gz-yami mall4j, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-108691 exists.

Affected product: gz-yami mall4j. 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-108691/ (Markdown: https://insights.sbomify.com/CVE-2026-108691/index.md)
```

## Sources

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

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