Security readout for executives and security teams
Plain-English summary
CVE-2025-55371 is an access-control flaw in jshERP v3.5. The public CVE says unauthenticated attackers can call a PersonController method and obtain handler information. The reported impact is limited confidentiality exposure, not data modification or outage. The affected-product metadata is incomplete, so teams should confirm whether they run jshERP v3.5.
Executive priority
Treat as a moderate-priority exposure review. It does not indicate system takeover or active exploitation in the supplied sources, but unauthenticated information disclosure in an ERP system can expose sensitive operational data. Prioritize internet-facing or broadly accessible instances first.
Technical view
The issue is classified as CWE-284. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and no user interaction required. The described vulnerable area is /controller/PersonController.java, where getAllList may expose handler information without proper authorization. No integrity or availability impact is stated.
Likely exposure
Most relevant to organizations running internet-accessible or internally shared jshERP v3.5 instances. The CVE record's affected vendor/product fields are n/a, but the title and references identify jshERP v3.5 and PersonController.java. Exposure is lower where the application is isolated and access is tightly controlled.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. The public description indicates exploitation requires network reachability and no credentials, which makes exposed deployments worth checking. The referenced researcher page may contain more operational detail, but this assessment avoids exploit guidance.
Researcher notes
Evidence is limited. The CVE affected-product fields are not populated, while the title and references identify jshERP v3.5. No official patch, fixed version, or vendor advisory is named in the supplied bundle. Validate directly against deployed code and vendor repository history before asserting remediation status.
Mitigation direction
- Confirm whether jshERP v3.5 is deployed in any environment.
- Check upstream jshERP guidance for patches, configuration changes, or fixed releases.
- Restrict access to jshERP behind trusted networks or identity-aware controls.
- Review authorization checks around PersonController and getAllList before exposure.
- Monitor application logs for unusual unauthenticated access to person-related controller routes.
Validation and detection
- Inventory running jshERP versions and flag any v3.5 deployments.
- Review PersonController.java to confirm getAllList enforces authentication and role authorization.
- Test with approved internal procedures that unauthenticated users cannot access handler lists.
- Check web and application logs for unexpected access to affected controller paths.
- Document whether compensating network controls limit reachable attack surface.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupCVE-2025-55371 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/jishenghua/jshERPCVE reference, mitre
- https://github.com/cina666/CVE/blob/main/jshERP/%E8%B6%8A%E6%9D%83%E8%87%B4%E4%BB%BB%E6%84%8F%E6%8E%A5%E7%AE%A1%E8%B4%A6%E5%8F%B7.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.