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-102362 Overview
CVE-2026-102362 is a missing authentication vulnerability [CWE-306] affecting mall4j through version 4.0, an open-source e-commerce platform maintained by gz-yami. The DELETE /prodComm endpoint in ProdCommController does not enforce authentication or authorization checks. Unauthenticated remote attackers can delete arbitrary product reviews by submitting the target prodCommId parameter. The flaw allows attackers to tamper with merchant reputation data and remove legitimate customer feedback without credentials.
Critical Impact
Any unauthenticated attacker with network access to a mall4j deployment can delete arbitrary product reviews, resulting in integrity loss for merchant catalog data.
Affected Products
- mall4j through 4.0 (gz-yami)
- yami-shop-api module containing ProdCommController
- Deployments exposing the DELETE /prodComm endpoint to untrusted networks
Discovery Timeline
- 2026-09-29 - CVE-2026-102362 published to the National Vulnerability Database
- 2026-09-30 - Last updated in NVD database
Technical Details for CVE-2026-102362
Vulnerability Analysis
The vulnerability resides in the ProdCommController class within the yami-shop-api module of mall4j. The controller exposes a DELETE /prodComm handler that accepts a prodCommId parameter identifying the product comment to remove. The handler executes the delete operation without verifying the caller's identity or confirming ownership of the target review.
Because the endpoint lacks an authentication filter and does not validate that the requester created the comment, any remote client can iterate prodCommId values and purge reviews at will. The impact is scoped to data integrity, allowing attackers to remove negative feedback, competitor reviews, or entire comment histories. Confidentiality and availability of the broader application remain unaffected. See the VulnCheck Advisory for Mall4j for additional context.
Root Cause
The root cause is missing authentication on a state-changing HTTP endpoint [CWE-306]. The ProdCommController delete handler is not annotated with an authentication requirement, and no authorization check compares the current session subject to the owner of the referenced prodCommId. Review the vulnerable handler in the GitHub ProdCommController Code Reference.
Attack Vector
Exploitation requires only network reachability to the mall4j API. An attacker issues an HTTP DELETE request to /prodComm with a valid prodCommId value and no authentication header. The server executes the deletion and returns a success response. A public proof of concept is available in the GitHub PoC for CVE Request.
No verified exploit code is reproduced here. Refer to the linked PoC for technical details.
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-102362
Indicators of Compromise
- Unexpected DELETE /prodComm requests in application access logs, particularly from IPs without prior authenticated session activity
- Missing Authorization or session cookie headers on successful DELETE /prodComm responses
- Database audit records showing bulk removal of rows from the product comment table with no associated administrator session
Detection Strategies
- Alert on any HTTP DELETE request to /prodComm that lacks a valid session token or originates from an unauthenticated client
- Correlate spikes in product review deletions with source IP reputation and geographic anomalies
- Baseline the normal daily volume of comment deletions per merchant and flag statistical outliers
Monitoring Recommendations
- Enable verbose logging on the yami-shop-api service, including request method, path, source IP, and authentication state
- Forward web server and application logs to a centralized analytics platform for retention and query
- Monitor egress from application servers for signs of scripted enumeration of prodCommId values
How to Mitigate CVE-2026-102362
Immediate Actions Required
- Restrict network exposure of the mall4j API to trusted clients using a web application firewall or reverse proxy access control list
- Block unauthenticated DELETE requests to /prodComm at the edge until a patched build is deployed
- Review product comment tables for unauthorized deletions and restore from backups where necessary
Patch Information
As of the last NVD update on 2026-09-30, no vendor patch is referenced in the advisory. Monitor the GitHub Repository for Mall4j for upstream fixes and the VulnCheck Advisory for Mall4j for remediation guidance.
Workarounds
- Add a server-side authentication filter that requires a valid session for the DELETE /prodComm route in ProdCommController
- Implement an authorization check that verifies the authenticated user is the original author of the comment referenced by prodCommId, or holds an administrator role
- Deploy a WAF rule that denies DELETE requests to /prodComm when no session cookie or bearer token is present
# Example NGINX rule to block unauthenticated DELETE /prodComm requests
location = /prodComm {
if ($request_method = DELETE) {
if ($http_authorization = "") { return 401; }
}
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

