jshERP: Authorization Bypass Through User-Controlled Key
CVE-2025-7947 is a high-severity authorization bypass through user-controlled key vulnerability in jshERP, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected jshERP versions: 3.0; 3.1; 3.2, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of jshERP you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 2.1 | Low | CNA (vuldb.com) |
| CVSS 3.1 | 5.4 | Medium | CNA (vuldb.com) |
| CVSS 3.1 | 8.1 | High | NVD |
| CVSS 2.0 | 5.5 | Medium | CNA (vuldb.com) |
Official description
A vulnerability classified as critical has been found in jshERP up to 3.5. Affected is an unknown function of the file /user/delete of the component Account Handler. The manipulation of the argument ID leads to improper authorization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How developers prevent this class of flaw
- For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
More Authorization Bypass Through User-Controlled Key vulnerabilities (CWE-639)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- vuldb.com/?id.317088Third Party Advisory, VDB Entry
- vuldb.com/?submit.619276Third Party Advisory, VDB Entry
Technical write-ups (may include proof of concept)
- github.com/jishenghua/jshERP/issues/124Exploit, Issue Tracking
Other references
- vuldb.com/?ctiid.317088Permissions Required, VDB Entry
Other vulnerabilities in jshERP
- 8.8 High severity
- 7.2 High severity
Recent Authorization Bypass Through User-Controlled Key vulnerabilities
- 8.7 High severity
- 7.5 High severity
- 7.1 High severity
- 7.5 High severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.