Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege jshERP user
-
ExploitSend GET to /log/list or /log/info
-
ExecutionMissing authorization check in LogController returns tenant audit log
-
ImpactHarvest other users' login names, IPs, and actions
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must possess valid credentials for any low-privilege account on the target jshERP instance (PR:L). Given such an account, the LogController endpoints /log/list and /log/info perform no per-user/role authorization check (CWE-862), so any authenticated user can read the full tenant operation audit log. Exploitation is remote over HTTP with no user interaction and no non-default configuration required; the primary limiting factor is the need for a pre-existing authenticated account, which confines the threat to insiders or attackers who have already obtained low-privilege access. Impact is limited to disclosure of audit metadata (login names, client IPs, actions) - no write, integrity, or availability effect is described. |
| Impact | This is a low-to-moderate priority information-disclosure issue, not an urgent emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) and the 5.3 base score are internally consistent with the description: a network-reachable, low-complexity read performed by an already-authenticated low-privilege user, with only limited confidentiality impact (VC:L) and no integrity or availability impact. The PR:L metric correctly reflects that this is an authorization flaw (CWE-862), not an unauthenticated authentication bypass - the attacker must first hold a valid account. Publicly available exploit code exists (GitHub POC), which raises practical exploitability, but there is no EPSS score provided and no CISA KEV listing, so there is no public exploit identified as actively exploited at time of analysis; the signals point to proof-of-concept availability rather than confirmed mass exploitation. One conflict to verify: the POC filename references 'message tampering' in addition to audit-log reading, which would imply integrity impact beyond the read-only disclosure described by NVD/VulnCheck - the input description and CVSS (VI:N) only support confidentiality disclosure, so any tampering claim should be verified with the vendor/VulnCheck advisory before being treated as fact. |
| Exploit ScenarioDerived | An attacker who holds any low-privilege account on a jshERP (≤3.6) tenant sends a simple GET request to /log/list or /log/info and receives the tenant's operation audit log, exposing other users' login names, client IP addresses, and actions. A publicly available POC exists, so exploitation requires only valid credentials and a standard HTTP client, with no user interaction and low attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 12, 2026
Any authenticated low-privilege user of jshERP through 3.6 can read the tenant-wide operation audit log because the LogController endpoints /log/list and /log/info validate that a session exists but never check the caller's role or ownership of the records (CWE-862 missing authorization). A single valid account, including one with minimal privileges, is therefore enough to harvest other users' login names, client IP addresses, and recorded actions over plain HTTP GET requests, with no user interaction and no non-default configuration required. Publicly available exploit code exists (a PoC script published alongside the request that also references message tampering), but the vulnerability is not confirmed as actively exploited and the assessed impact is limited to information disclosure - no integrity or availability effect - giving a CVSS 4.0 base score of 5.3 and an assessed CVSS 3.1 score of 5.3, a low-to-moderate priority disclosure issue rather than an emergency.
RemediationAI
No vendor-released patch was identified at time of analysis, so operators should treat the /log/list and /log/info endpoints as privileged and restrict them themselves. The most direct compensating control is to front jshERP with a reverse proxy, API gateway, or WAF rule that blocks or role-gates GET requests to those two paths for anything other than an administrator identity - the trade-off is that path-based filtering depends on trustworthy identity signals (for example mTLS, a hardened session cookie check, or IP allow-listing), so it must be tested to avoid breaking the legitimate admin audit-log view. Where source changes are feasible, a build-time fix is to add an explicit role or tenant-ownership check in LogController (or a Spring Security/interceptor mapping limited to the admin role) before delegating to LogService, accepting the maintenance burden of a forked build until upstream ships a fix. Alongside these controls, reduce the number of low-privilege accounts issued, rotate credentials and review account provisioning because the leaked login names and client IPs materially aid follow-on credential attacks, and monitor web logs for repeated or scripted GETs against /log endpoints, which is the observable signature of the published PoC. Consult the advisory at https://www.vulncheck.com/advisories/jsherp-through-3.6-missing-authorization-via-log-list-and-log-info and the upstream source references for confirmation of any future patched release before relying on a vendor version number that is not yet documented.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
jshERP is an open-source Java enterprise resource planning suite whose backend service (jshERP-boot) exposes a Spring-based REST API. The affected code paths are the LogController request handlers at lines 40-68 and the matching LogService logic at lines 41-80 in the upstream repository commit 8f28e7c2fe54d54de3621a414f5df1833dc5a55f, which retrieve audit records for the current tenant without filtering them by the requesting principal. The root cause class is CWE-862 (Missing Authorization): authentication is enforced framework-wide, but this controller omits the per-role or per-user permission check applied elsewhere in the application, so the audit log is treated as a global tenant resource rather than a privileged one. Both the CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N) and the independent assessment (CVSS 3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) agree the attack is remote, low complexity, requires low privileges, needs no user interaction, and results only in low confidentiality loss - the PR:L metric confirms the endpoints are reachable by authenticated users, though only with an already-valid account.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Authenticated low-privilege user (PR:L) makes a simple network HTTP request (AV:N/AC:L/UI:N); only limited audit-metadata confidentiality is exposed, so C:L with I:N/A:N.
Primary rating from Vendor (vulncheck).
CVSS VectorVendor: vulncheck
DescriptionCVE.org
jshERP through 3.6 contains a missing authorization vulnerability in LogController that allows any authenticated user to read the tenant's operation audit log. Low-privilege users can send GET requests to /log/list or /log/info to view other users' login names, client IP addresses, and actions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-97383
GHSA-2728-wh22-wmw9
NVD
CVE.org
EPSS
Exploit-DB