Skip to main content
VulnerabilityPublished

CVE-2025-7948: jshERP · Weak Password Recovery

Affects jshERPSource CVE Database V5

0

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 15:59 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubjishenghua/jshERPpkg:github/jishenghua/jshERPOther threatsAffected
  • 3.0 – 3.5
6 affected builds
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 immediately audit their jshERP deployments to identify affected versions (3.0 through 3.5). Since no official patches are currently linked, mitigation should focus on compensating controls: 1) Restrict network access to the /jshERP-boot/user/updatePwd endpoint using firewalls or web application firewalls (WAFs) to limit exposure to trusted IP addresses only. 2) Implement multi-factor authentication (MFA) on user accounts to reduce the impact of password recovery bypass. 3) Monitor logs for unusual password reset activities or multiple failed attempts targeting the recovery endpoint. 4) Temporarily disable or restrict password recovery functionality if feasible until a patch is available. 5) Engage with the jshERP vendor or community for updates or patches addressing this vulnerability. 6) Educate users on reporting suspicious account activities promptly. 7) Conduct penetration testing focused on password recovery workflows to identify any additional weaknesses. These targeted mitigations go beyond generic advice by focusing on access control, monitoring, and user awareness specific to the vulnerable functionality.

Description

A vulnerability classified as problematic was found in jshERP up to 3.5. Affected by this vulnerability is an unknown functionality of the file /jshERP-boot/user/updatePwd. The manipulation leads to weak password recovery. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.

References

Community reviews

Loading reviews…