jishenghua jshERP 3.6 updateOneValueByKeyIdAndType endpoint poc-01-userbusiness-self-privilege-escalation.py type/user ID/role ID list privileges management

Summaryinfo

A vulnerability was found in jishenghua jshERP 3.6. It has been rated as critical. The affected element is the function updateOneValueByKeyIdAndType of the file poc-01-userbusiness-self-privilege-escalation.py of the component updateOneValueByKeyIdAndType endpoint. This manipulation of the argument type/user ID/role ID list causes privileges management. This vulnerability is registered as CVE-2026-94411. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in jishenghua jshERP 3.6. Affected by this vulnerability is the function updateOneValueByKeyIdAndType of the file poc-01-userbusiness-self-privilege-escalation.py of the component updateOneValueByKeyIdAndType endpoint. The manipulation of the argument type/user ID/role ID list with an unknown input leads to a privileges management vulnerability. The CWE definition for the vulnerability is CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-94411 since 09/21/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/21/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• jishenghua

Name

• jshERP

Version

• 3.6

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion