CVE-2026-94497
8.3jshERP · jshERP
jshERP versions 3.6 and earlier suffer from an insecure direct object reference vulnerability, allowing authenticated users to access and modify business objects belonging to other users.
Executive summary
A critical authorization bypass in jshERP 3.6 and earlier allows authenticated users to perform unauthorized read, update, and delete operations on business data belonging to other tenants.
Vulnerability
The application fails to perform authorization checks when processing requests to info, update, and delete endpoints. By manipulating direct object identifiers, any authenticated user can interact with objects they do not own, bypassing cross-tenant data isolation.
Business impact
The ability for low-privileged users to modify or delete sensitive business records poses a severe risk to data integrity and operational continuity. Given the CVSS score of 8.3, this high-severity flaw could lead to the unauthorized exposure of proprietary information, financial data corruption, or the permanent loss of business records.
Remediation
Immediate Action: Update to the latest version of jshERP as provided by the vendor to resolve the missing authorization checks. If an update is not immediately available, restrict access to the application to trusted users only.
Proactive Monitoring: Review application access logs for anomalous patterns, such as a single user account requesting or modifying a high volume of sequential object IDs, which may indicate exploitation attempts.
Compensating Controls: Implement a Web Application Firewall (WAF) to detect and block requests that attempt to access restricted API endpoints or manipulate object identifiers in an unauthorized manner.
Exploitation status
Public Exploit Available: Yes — a functional proof-of-concept script has been published on GitHub.
Analyst recommendation
This vulnerability represents a significant risk to organizational data security due to the ease with which attackers can manipulate business objects. Administrators should prioritize patching their jshERP instances immediately to prevent unauthorized data tampering and ensure that proper authorization logic is enforced across all API endpoints.
More jshERP CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section
Sources
Originally found and disclosed by Mingsheng Lin, per the CVE Program record.
- Proof of concept Exploit / PoC
- Vulnerable code Technical analysis
- github.com
- VulnCheck Advisory: jshERP through 3.6 Unauthorized Access via by-id Endpoints Third-party advisory