Loading vulnerability…
Incorrect access control in the /jshERP-boot/user/info interface of jshERP up to commit 90c411a allows attackers to access sensitive information via a crafted GET request.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This four-file repository is a standalone VulDB submission package, not a framework module. It contains documentation (.gitignore, README.md, and a detailed VULDB_REPORT.md) plus poc.sh, a Bash proof of concept. The PoC targets jshERP/jshERP-boot 3.6-SNAPSHOT at the documented master commit and the v3.6 tag. It authenticates as the hard-coded low-privilege test account, enumerates tenant user IDs, calls the authenticated GET /user/info endpoint with a caller-controlled target ID, and extracts the returned password field. Because jshERP's login flow accepts the stored client-side MD5 digest directly, the script replays the disclosed digest to log in as the selected target (jsh in the lab), then verifies the new session and compares role functions. The underlying issue is an authenticated object-level authorization failure: UserService.getUser(id) verifies only that a caller has a session, rather than restricting the requested ID to the caller or requiring user-management permission. The report identifies credential exposure as the direct result and account takeover/privilege escalation as the practical impact. CVE-2025-60800 is cited as a related prior unauthenticated traversal issue, while this repository specifically claims the residual authenticated IDOR after that traversal filter was addressed.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.