# CVE-2026-94496: jshERP through 3.6 Privilege Escalation via Role Management

> Authenticated users can escalate privileges and access all business records by exploiting missing permission checks in role management endpoints.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/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-g2pg-97r2-r2p9

## What is CVE-2026-94496?

CVE-2026-94496 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 fails to validate caller permissions in role management endpoints, allowing authenticated users to modify any role's data scope or delete roles. Attackers can exploit the /role/update and /role/delete endpoints to escalate privileges, change data visibility to all data, and access all business records in the tenant.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94496 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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