# CVE-2026-109184: jshERP through 3.6 Data Scope Bypass via /account/findAccountInOutList

> Low-privilege users can bypass data scope restrictions to view other users' financial ledger details in jshERP.

- **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:** 13 Oct 2026
- **Also known as:** GHSA-x2p6-gwmm-696c

## What is CVE-2026-109184?

CVE-2026-109184 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 improper authorization vulnerability that allows low-privilege authenticated users to read any settlement account ledger by supplying an arbitrary accountId. Attackers restricted to personal or department data scope can query GET /account/findAccountInOutList to view other users' bill numbers, counterparties, amounts and remarks within the tenant.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-109184 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109184 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-109184 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-109184/ (Markdown: https://insights.sbomify.com/CVE-2026-109184/index.md)
```

## Sources

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

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