CVE-2025-55370: Incorrect access control in the component \controller\ResourceController.java of jshERP v3.5 allows unautho...
Incorrect access control in the component \controller\ResourceController.java of jshERP v3.5 allows unauthorized attackers to obtain all the corresponding ID data by modifying the ID value.
Security readout for executives and security teams
Plain-English summary
CVE-2025-55370 is an access-control flaw reported in jshERP v3.5. An attacker may change an ID value and retrieve data tied to other accounts. For an ERP system, that can expose sensitive business and user information and may support unauthorized account access, depending on deployment.
Executive priority
Prioritize assessment for any jshERP v3.5 system handling customer, financial, inventory, or account data. The issue is high severity and may undermine ERP data confidentiality and integrity, but the supplied evidence does not confirm active exploitation or a named patch.
Technical view
The record describes CWE-639 in \controller\ResourceController.java: authorization appears tied insufficiently to caller context, allowing object access by modifying an ID. CVSS 3.1 is 8.8 high. The CVE metadata lists affected vendor/product as n/a, but the description and references identify jshERP v3.5.
Likely exposure
Exposure is most likely where jshERP v3.5 is deployed and the affected ResourceController functionality is reachable. Internet-facing ERP portals are higher concern. Because official CPE and affected-product fields are absent, teams should confirm exposure through application inventory, version checks, and code or route review.
Exploitation context
The bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub writeup is referenced, indicating public technical discussion exists. Treat this as high-risk but do not claim real-world exploitation from the supplied evidence.
Researcher notes
Key uncertainty is metadata quality: affected vendor/product/CPE fields are n/a while the narrative names jshERP v3.5. The CVSS vector includes PR:N and UI:R. Validate authorization behavior defensively and avoid assuming broader version impact without vendor confirmation.
Mitigation direction
Check jshERP vendor or project guidance for a fixed release or advisory.
Limit external access to jshERP until remediation is confirmed.
Enforce server-side authorization for every resource ID lookup.
Review ResourceController.java for caller-to-object ownership checks.
Monitor ERP access logs for unusual ID enumeration patterns.
Validation and detection
Inventory all jshERP deployments and identify any v3.5 instances.
Confirm whether ResourceController endpoints are reachable by untrusted users.
Verify cross-account resource IDs are rejected server-side.
Review logs for repeated changed ID values or account-data access anomalies.
Track the CVE record and jshERP repository for update guidance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.