PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

New CVE Detected

CVE-2026-102361 – Authentication Bypass / Account Takeover – mall4j ≤ 4.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-102361 is a critical missing-authentication vulnerability in mall4j, an open-source e-commerce platform maintained by gz-yami. The PUT /user/updatePwd endpoint allows an unauthenticated attacker to reset the password of any storefront account by supplying that account’s identifier in the request body, resulting in full account takeover. The issue affects mall4j through version 4.0 and carries a CVSS score of 9.3 (Critical).

Technical details

  • Root cause: The updatePwd method in UserRegisterController (part of the yami-shop-api module) processes password-change requests without verifying that the caller is authenticated as, or otherwise authorized to act on behalf of, the target account.
  • Trigger conditions: The handler looks up the target user record by identifier, decrypts the attacker-supplied new password, encodes it, and writes it to the database — with no session/token check tying the request to the account owner.
  • Attack vector: Network-based (AV:N), no privileges or user interaction required. An attacker sends a crafted PUT /user/updatePwd request containing a target user’s identifier and an arbitrary new password.
  • Impact: Complete account takeover of any storefront user, exposing customer orders and personal data, and enabling further fraud or lateral abuse of the compromised account.

Affected software

  • mall4j (gz-yami/mall4j), all versions through 4.0

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical) — AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CVSS v4.0 Score (as rated): 9.3 (Critical) — AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N
  • CWE-306: Missing Authentication for Critical Function

Mitigation and recommended actions

  • Immediate: Upgrade mall4j to a version where the /user/updatePwd endpoint enforces authentication and verifies that the requester owns the target account. Check the gz-yami/mall4j repository for a patched release addressing this endpoint, as no fixed version number has been published at the time of writing.
  • If no patch is available: Restrict or disable public access to the /user/updatePwd endpoint at the network/WAF layer until a fix is applied, and add server-side logic requiring a valid authenticated session (or a signed password-reset token tied to the account) before any password change is processed.
  • Monitor authentication logs for unexpected password-change activity on the storefront and force a password reset/re-authentication for accounts that may have been affected.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge