# CVE-2026-111615: Mall4cloud through 4.0 IDOR Exposing Buyer Addresses via order_addr Endpoint

> Authenticated merchants can enumerate order IDs to access other shops' buyer shipping addresses and personal details.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/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:** 16 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-96x2-4759-fjj4

## What is CVE-2026-111615?

CVE-2026-111615 is a high-severity vulnerability in gz-yami mall4cloud, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mall4cloud through 4.0 contains an insecure direct object reference vulnerability that allows authenticated merchants to read other shops' buyer shipping addresses via the multishop OrderController getOrderAddr handler. Attackers can enumerate auto-increment orderAddrId values in GET /m/order/order_addr/{orderAddrId} requests to obtain consignee names, mobile numbers, addresses and post codes platform-wide.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111615 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111615 is a high-severity vulnerability in gz-yami mall4cloud, published on 16 Oct 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-111615 exists.

Affected product: gz-yami mall4cloud. 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-111615/ (Markdown: https://insights.sbomify.com/CVE-2026-111615/index.md)
```

## Sources

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

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