Quick answers
- Is CVE-2025-55367 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-55367 being exploited in the wild.
- How severe is CVE-2025-55367?
- Medium severity, with a CVSS score of 5.3, published 21 August 2025.
- Which products and versions are affected?
- Jishenghua jshERP 3.5.
- Is there a fix for CVE-2025-55367?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-55367 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-55367?
- Check whether you run Jishenghua jshERP at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An improper access control vulnerability exists in the batchSetStatus method within the SupplierController.java component of jshERP v3.5. The flaw allows an attacker to perform path traversal (using /../ sequences) to reach the supplier management endpoint without a valid X-Access-Token. By sending a specially crafted HTTP request to the /jshERP-boot/user/login/../../supplier/batchSetStatus path, an unauthenticated remote attacker can modify the 'status' field for any supplier ID. This results in a horizontal privilege escalation where an attacker can manipulate vendor data belonging to any tenant or account.
Affected products
- jishenghua jshERP 3.5
Timeline
- 2025-08-21: advisory
- 2025-08-21: disclosed