# CVE-2026-102364: mall4j through 4.0 Improper Authentication Accepts Storefront Tokens on Admin API

> Attackers can reuse storefront session tokens to access admin endpoints, enabling privilege escalation and unauthorized data access in mall4j.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-7f4q-fvgh-44w4

## What is CVE-2026-102364?

CVE-2026-102364 is a medium-severity authentication bypass vulnerability in gz-yami mall4j, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

mall4j through 4.0 fails to validate the sysType field in sa-token sessions, allowing storefront customers to authenticate as back-office users by reusing their session tokens. Attackers can register on the public storefront and use their customer session token to access admin endpoints lacking @PreAuthorize permission checks, including menu listings, file uploads, and configuration endpoints.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-102364 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102364 is a medium-severity authentication bypass vulnerability in gz-yami mall4j, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102364 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-102364/ (Markdown: https://insights.sbomify.com/CVE-2026-102364/index.md)
```

## Sources

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

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