# CVE-2026-109182: jshERP through 3.6 Incorrect Authorization via /supplier/exportExcel

> Authenticated users can bypass role restrictions to export all supplier, customer, and member records, exposing sensitive contact and financial data.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/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:** 12 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-jqh7-3f4j-wvmx

## What is CVE-2026-109182?

CVE-2026-109182 is a medium-severity missing authorization vulnerability in jishenghua jshERP, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

jshERP through 3.6 contains an incorrect authorization vulnerability in GET /supplier/exportExcel that allows authenticated users to bypass role data scope restrictions enforced by /supplier/list. Attackers restricted to personal or department data can export every supplier, customer and member record, exposing contacts, phone numbers, tax numbers, bank accounts and balances.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-109182 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109182 is a medium-severity missing authorization vulnerability in jishenghua jshERP, published on 12 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-109182 exists.

Affected product: jishenghua jshERP. 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-109182/ (Markdown: https://insights.sbomify.com/CVE-2026-109182/index.md)
```

## Sources

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

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