# CVE-2026-102361: mall4j through 4.0 Missing Authentication in Password Update Endpoint

> Unauthenticated attackers can reset any user's password via the updatePwd endpoint, leading to account takeover and access to personal data.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-97hh-9379-xqmm

## What is CVE-2026-102361?

CVE-2026-102361 is a critical missing authorization vulnerability in gz-yami mall4j, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mall4j through 4.0 contains a missing authentication vulnerability in the PUT /user/updatePwd endpoint that allows unauthenticated attackers to reset any storefront account password. Attackers can supply a target username in the request body to overwrite passwords without verification, enabling account takeover and access to orders and personal data.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-102361?


## How do I fix CVE-2026-102361?

No fix has been published for CVE-2026-102361 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-102361 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102361 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102361 and fix it if it is affected.

What it is: CVE-2026-102361 is a critical missing authorization vulnerability in gz-yami mall4j, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102361 exists.

Affected product: gz-yami mall4j. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102361/ (Markdown: https://insights.sbomify.com/CVE-2026-102361/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102361
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102361
- OSV: https://osv.dev/vulnerability/CVE-2026-102361

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102361/
Summaries are generated and may contain mistakes; the official description above is the record.