CVE-2025-67344: jshERP · n/a
Affects jshERPSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjishenghua/jshERPpkg:github/jishenghua/jshERPOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should implement strict input validation and output encoding on the /msg/add endpoint to prevent malicious script injection. Employing Content Security Policy (CSP) headers can help mitigate the impact of XSS by restricting script execution sources. Restricting user privileges to the minimum necessary can reduce the likelihood of exploitation, as this vulnerability requires low privileges but authenticated access. Monitoring logs for unusual activity related to message submissions and user interactions can provide early detection of exploitation attempts. Until official patches are released, consider disabling or restricting access to the vulnerable endpoint if feasible. Conduct security awareness training to inform users about the risks of interacting with untrusted content. Regularly update and audit ERP systems to ensure timely application of security fixes once available. Finally, implement web application firewalls (WAFs) with rules targeting XSS attack patterns to provide an additional layer of defense.
Description
jshERP v3.5 and earlier is affected by a stored Cross Site Scripting (XSS) vulnerability via the /msg/add endpoint.