# CVE-2026-94501: jshERP through 3.6 Privilege Escalation via userBusiness CRUD

> Authenticated users can bypass authorization checks in userBusiness CRUD endpoints to escalate privileges or modify access controls for any user.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 21 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-pvxx-75wv-6w9m

## What is CVE-2026-94501?

CVE-2026-94501 is a high-severity missing authorization vulnerability in jishenghua jshERP, published on 21 Sep 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 authorization bypass vulnerability in the userBusiness CRUD endpoints that allows authenticated users to create, modify, or delete authorization-relation rows without privilege checks. Attackers can manipulate user-role mappings and access controls to escalate privileges, strip access from other accounts, or modify role-function relationships for any user in the tenant.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94501 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94501 is a high-severity missing authorization vulnerability in jishenghua jshERP, published on 21 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-94501 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-94501/ (Markdown: https://insights.sbomify.com/CVE-2026-94501/index.md)
```

## Sources

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

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