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-102363 Overview
CVE-2026-102363 is a missing authentication vulnerability [CWE-306] in the mall4j e-commerce platform through version 4.0. The flaw resides in the DeliveryController.checkDelivery endpoint, which exposes shipment tracking data without validating the caller's identity or order ownership. An unauthenticated attacker who supplies a valid order number can retrieve carrier names, waybill numbers, and complete logistics trails for that order. The issue affects the yami-shop-api module of the open-source mall4j project maintained by gz-yami.
Critical Impact
Any remote, unauthenticated attacker can enumerate order numbers to harvest shipping details for arbitrary customers, enabling downstream fraud, phishing, and package interception.
Affected Products
- mall4j through 4.0 (yami-shop-api)
- DeliveryController component in the gz-yami/mall4j repository
- Deployments exposing the checkDelivery endpoint to untrusted networks
Discovery Timeline
- 2026-09-29 - CVE-2026-102363 published to NVD
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-102363
Vulnerability Analysis
The vulnerability is a broken access control issue in a REST endpoint of the mall4j Java application. The checkDelivery handler in DeliveryController.java accepts an order number parameter and returns the associated shipment tracking record. The handler performs no authentication check and does not confirm that the requester owns the referenced order. As a result, the endpoint behaves as an anonymous data source for any order whose identifier can be guessed or enumerated. Because tracking data includes carrier identity and waybill numbers, attackers can pivot to carrier portals or craft targeted phishing messages against buyers.
Root Cause
The root cause is a missing authentication and authorization control on a business endpoint that returns customer data. The route is registered in the API layer without a security annotation or session check, and the underlying service does not filter results by the authenticated user. This maps directly to [CWE-306: Missing Authentication for Critical Function].
Attack Vector
Exploitation requires only network access to the mall4j API and knowledge or guess of an order number. An attacker sends an HTTP request to the checkDelivery endpoint with an orderNumber parameter and receives the tracking response in JSON. Order numbers are typically sequential or predictably formatted, so enumeration is straightforward. A public proof-of-concept script, A08_delivery_check_anonymous.py, demonstrates the request pattern against the vulnerable route. See the VulnCheck Advisory and the DeliveryController source for the vulnerable code path.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-102363
Indicators of Compromise
- Unauthenticated HTTP requests to /delivery/checkDelivery or equivalent paths bearing an orderNumber query parameter.
- Bursts of sequential order-number requests from a single source IP, indicative of enumeration.
- Access-log entries returning HTTP 200 responses with tracking payloads but lacking a session cookie or Authorization header.
Detection Strategies
- Inspect application access logs for requests to the checkDelivery route that arrive without an authenticated session token.
- Deploy a WAF rule that flags high request rates against delivery or order lookup endpoints from a single client.
- Correlate API access telemetry with order-database reads to identify anonymous lookups of customer data.
Monitoring Recommendations
- Ship API gateway and reverse-proxy logs to a central analytics platform and alert on unauthenticated hits to order-lookup endpoints.
- Baseline normal request volume for checkDelivery and alert on statistical deviations that suggest enumeration.
- Monitor egress patterns from mall4j hosts for indicators that harvested data is being exfiltrated to attacker infrastructure.
How to Mitigate CVE-2026-102363
Immediate Actions Required
- Restrict network access to the checkDelivery endpoint using a reverse proxy or WAF until an upstream fix is available.
- Require an authenticated session and validate that the caller owns the requested order before returning tracking data.
- Rate-limit the endpoint to slow order-number enumeration by unauthenticated clients.
Patch Information
No vendor-supplied patch is referenced in the advisory at publication time. Track the gz-yami/mall4j repository for updates to DeliveryController.java and apply fixes to the yami-shop-api module as they land. Operators building from source should add a server-side authentication check and an ownership filter to the checkDelivery handler.
Workarounds
- Add an authentication filter or Spring Security annotation to the checkDelivery route so it rejects anonymous requests.
- Enforce order-ownership validation in the delivery service layer, keyed on the authenticated user identifier.
- Replace enumerable order numbers with high-entropy identifiers to reduce the value of brute-force lookups.
- Block or throttle access to the endpoint at the API gateway for clients without a valid session token.
# Example NGINX snippet to require an auth cookie on the vulnerable route
location /delivery/checkDelivery {
if ($cookie_SESSION = "") {
return 401;
}
limit_req zone=api_limit burst=10 nodelay;
proxy_pass http://mall4j_backend;
}
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

