Skip to main content
Vulnerability Database/CVE-2026-102361

CVE-2026-102361: mall4j Authentication Bypass Vulnerability

CVE-2026-102361 is an authentication bypass flaw in mall4j that enables attackers to reset any account password without verification. This post explains its technical details, affected versions, impact, and mitigation steps.

Published:

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-102361 Overview

CVE-2026-102361 is a missing authentication vulnerability [CWE-306] affecting the mall4j e-commerce platform through version 4.0. The flaw resides in the PUT /user/updatePwd endpoint, which fails to verify the identity of the requester before processing password changes. An unauthenticated attacker can supply an arbitrary target username in the request body and overwrite that account's password without any credential validation. Successful exploitation grants full account takeover of any storefront user, exposing order history, personal data, and stored payment information.

Critical Impact

Unauthenticated remote attackers can take over any storefront account by resetting its password through a single HTTP request, requiring no user interaction or prior access.

Affected Products

  • mall4j through version 4.0
  • yami-shop-api component (UserRegisterController)
  • Deployments exposing the storefront API to untrusted networks

Discovery Timeline

  • 2026-09-29 - CVE-2026-102361 published to NVD
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-102361

Vulnerability Analysis

The mall4j platform exposes a REST endpoint at PUT /user/updatePwd intended to let authenticated users change their own password. The endpoint accepts a JSON body containing a target username and a new password value. The controller does not validate that the requester owns the target account, nor does it enforce authentication on the route. As a result, any network-reachable client can submit a request naming a victim account and receive a successful password reset.

The vulnerability class is Missing Authentication for Critical Function [CWE-306]. It differs from a classic broken access control issue because no session token, JWT, or CSRF token is required at all. The endpoint is functionally an unauthenticated password-reset primitive available to the entire network attack surface.

Exploitation results in account takeover of any known or enumerable username. Because mall4j is used for e-commerce storefronts, compromised accounts yield order data, shipping addresses, phone numbers, and stored buyer information.

Root Cause

The root cause lies in the UserRegisterController handler for the password update route. The method reads the username directly from the request body and updates the corresponding record without cross-checking the authenticated principal. Combined with a permissive route configuration that omits the endpoint from the authentication filter chain, this produces a fully unauthenticated write to sensitive credential state.

Attack Vector

The attack vector is network-based and requires no privileges or user interaction. An attacker enumerates or guesses a valid storefront username, then issues a PUT request to /user/updatePwd with a JSON body containing the target username and a chosen password. The server responds with success and the attacker logs in with the new credentials. Public proof-of-concept code is published in the GitHub PoC repository, and the underlying handler is documented in the mall4j UserRegisterController source.

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 Attacks

Detection Methods for CVE-2026-102361

Indicators of Compromise

  • HTTP PUT requests to /user/updatePwd originating from unauthenticated sessions or unexpected IP ranges.
  • Password change events for storefront accounts without a preceding authenticated session or self-service reset workflow.
  • Sudden clusters of login successes from new geolocations immediately following /user/updatePwd traffic.
  • Customer complaints about lockouts or unauthorized order activity across multiple accounts in a short window.

Detection Strategies

  • Deploy web application firewall or reverse proxy rules that log every request to PUT /user/updatePwd with the source IP, User-Agent, and body username field.
  • Correlate application password-change audit records with authentication logs to flag resets that lack a valid prior session for the same user.
  • Alert on any single source IP invoking /user/updatePwd against multiple distinct usernames within a short interval, which indicates enumeration or mass takeover.

Monitoring Recommendations

  • Forward mall4j application logs and reverse-proxy access logs to a centralized SIEM for retention and correlation.
  • Baseline the normal rate of password changes per hour and trigger alerts when the rate exceeds two standard deviations.
  • Monitor downstream systems such as order management for spikes in address or payment-method changes that follow password resets.

How to Mitigate CVE-2026-102361

Immediate Actions Required

  • Block or restrict access to the PUT /user/updatePwd endpoint at the reverse proxy or web application firewall until a patched build is deployed.
  • Force a password reset for all storefront accounts and invalidate active sessions to evict any attackers who may have already exploited the flaw.
  • Audit recent password change events and correlate them with order and profile changes to identify compromised accounts.
  • Review the VulnCheck advisory for the latest remediation guidance.

Patch Information

At the time of publication, no vendor-supplied fix has been referenced in the NVD entry. Operators should monitor the mall4j GitHub repository for an updated release that adds authentication and ownership checks to the updatePwd handler. Until an official patch is available, apply the compensating controls described below.

Workarounds

  • Add an authentication filter that requires a valid session token for PUT /user/updatePwd and rejects unauthenticated requests at the framework layer.
  • Modify the controller to derive the target username from the authenticated principal rather than from the request body, ignoring any client-supplied identifier.
  • Restrict the endpoint to internal networks or VPN-protected administrative interfaces where possible.
  • Introduce rate limiting and CAPTCHA challenges on password-change flows to slow automated exploitation attempts.
bash
# Example NGINX rule to block unauthenticated access to the vulnerable endpoint
location = /user/updatePwd {
    if ($http_authorization = "") { return 401; }
    limit_req zone=pwdreset burst=3 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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.