Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108690 Overview
CVE-2026-108690 is an information disclosure vulnerability in mall4j through version 4.0, an open-source e-commerce platform maintained by gz-yami. The flaw resides in the getShopCartExpiryItems SQL filter, where an operator precedence error causes the query to return cart data belonging to other users. Any authenticated storefront customer can issue a GET /p/shopCart/expiryProdList request and retrieve off-shelf basket entries from other shoppers. Exposed fields include product identifiers, SKU, quantity, shop information, and promoter card numbers. The weakness is tracked under [CWE-783: Operator Precedence Logic Error].
Critical Impact
Authenticated customers can read other shoppers' expired cart contents, exposing product selection data and promoter card associations across tenants of the storefront.
Affected Products
- mall4j through version 4.0 (gz-yami)
- yami-shop-api module - ShopCartController
- yami-shop-service module - BasketMapper.xml
Discovery Timeline
- 2026-10-11 - CVE-2026-108690 published to NVD
- 2026-10-16 - Last updated in NVD database
Technical Details for CVE-2026-108690
Vulnerability Analysis
The vulnerability resides in the SQL fragment that filters expired or off-shelf cart items for a given user. The MyBatis mapper defined in BasketMapper.xml combines boolean conditions without proper grouping. As a result, the user-scoping predicate is not applied to all branches of the WHERE clause. The backend therefore returns basket rows that belong to arbitrary shoppers whenever an authenticated client calls the expiry list endpoint.
The exposed payload includes product references, SKU identifiers, quantities, shop context, and promoter card numbers. These values can be aggregated to profile active shoppers, map promoter programs, or support targeted follow-on attacks against the storefront. Exploitation only requires a valid storefront account, which can typically be self-registered.
Root Cause
The root cause is an operator precedence logic error ([CWE-783]) in the getShopCartExpiryItems SQL fragment used by BasketMapper.xml. Mixed AND and OR conditions without parentheses cause the SQL engine to evaluate the user filter at a different scope than intended. The ownership check is bypassed for a subset of rows, allowing cross-user data to flow back through the API.
Attack Vector
An attacker registers or authenticates as a normal storefront customer and sends a GET /p/shopCart/expiryProdList request with a valid session token. The ShopCartController method defined at lines 162-186 invokes the vulnerable mapper, which returns expiry basket entries from other users. No elevated privileges, user interaction, or unusual client state is required. See the GitHub PoC Script and the Vulncheck Advisory on Mall4j for complete request details.
// No verified exploitation code block included.
// Refer to the published PoC and advisory links above.
Detection Methods for CVE-2026-108690
Indicators of Compromise
- Repeated or automated GET /p/shopCart/expiryProdList requests from a single authenticated session.
- Responses containing basket entries whose userId or owning shopper identifier does not match the requesting account.
- Newly registered storefront accounts that query expiry-related endpoints shortly after sign-up.
Detection Strategies
- Instrument the ShopCartController.expiryProdList handler to log the authenticated user and every returned basket owner, then alert on mismatches.
- Deploy WAF or API gateway rules that rate-limit and inspect requests to /p/shopCart/expiryProdList.
- Review application logs for high-volume enumeration patterns against storefront customer APIs.
Monitoring Recommendations
- Enable verbose access logging for all /p/shopCart/* routes, including request headers and response row counts.
- Correlate storefront authentication events with cart API usage to flag abnormal access to expiry data.
- Track promoter card number appearances in API responses to detect bulk harvesting attempts.
How to Mitigate CVE-2026-108690
Immediate Actions Required
- Restrict or temporarily disable the /p/shopCart/expiryProdList endpoint until a verified patch is deployed.
- Review the getShopCartExpiryItems SQL fragment in BasketMapper.xml and add explicit parentheses around the user-scoping predicate.
- Audit storefront account provisioning to limit the number of accounts a single actor can create and abuse.
Patch Information
No official vendor patch is listed in the referenced advisories at time of publication. Operators should monitor the gz-yami/mall4j repository for updates to BasketMapper.xml and the ShopCartController, and review the Vulncheck Advisory on Mall4j for remediation guidance.
Workarounds
- Apply a hotfix to the BasketMapper.xml fragment to group boolean conditions with parentheses and enforce the user_id filter on every branch.
- Add a server-side ownership check in ShopCartController that filters the mapper result set by the authenticated user before returning it.
- Block the vulnerable route at the reverse proxy or API gateway for untrusted customer accounts until code changes ship.
# Example reverse-proxy block for the vulnerable endpoint
location = /p/shopCart/expiryProdList {
return 403;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

