# CVE-2026-94411: jshERP 3.6 Privilege Escalation via updateOneValueByKeyIdAndType

> Authenticated users can escalate privileges to tenant administrator by manipulating role assignment parameters in the updateOneValueByKeyIdAndType endpoint.

- **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:** 24 Sep 2026
- **Also known as:** GHSA-rv9h-p5p6-7pxh

## What is CVE-2026-94411?

CVE-2026-94411 is a high-severity 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 3.6 contains a privilege escalation vulnerability in the updateOneValueByKeyIdAndType endpoint that allows authenticated users to grant themselves arbitrary roles. Attackers can send a POST request with type=UserRole, their own user ID, and a role ID list to escalate from low-privilege tenant user to tenant administrator.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94411 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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