VulnerabilityPublished 11 Aug 2025

CVE-2025-8840: jshERP · Improper Authorization

Affects jshERPSource CVE Database V5

Mentioned vulnerabilities

CVE-2025-7947

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:07 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 39% 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:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
jshERP	Affected 3.0 – 3.5 6 affected builds	Fixed in–

AI-suggested

Immediate review and tightening of access control policies around the /jshERP-boot/user/deleteBatch endpoint to ensure only fully authorized administrators can invoke batch deletion functions.
Implement strict input validation and authorization checks on the 'ids' parameter to prevent unauthorized manipulation.
Monitor logs for unusual or bulk deletion requests, especially from accounts with limited privileges, to detect potential exploitation attempts early.
If possible, temporarily disable or restrict access to the deleteBatch functionality until an official patch or update is released.
Conduct a thorough audit of user privileges and remove unnecessary or excessive permissions to minimize the risk of privilege abuse.
Engage with the jshERP vendor or community to obtain or request a security patch addressing this vulnerability.
Educate administrators and users about the risks of this vulnerability and encourage vigilance against suspicious activity.
Consider implementing network-level controls such as web application firewalls (WAFs) to detect and block anomalous requests targeting this endpoint.

Description

A vulnerability was determined in jshERP up to 3.5. Affected is an unknown function of the file /jshERP-boot/user/deleteBatch of the component Endpoint. The manipulation of the argument ids leads to improper authorization. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. Different than CVE-2025-7947.

Impact

For European organizations using jshERP versions 3.0 to 3.5, this vulnerability poses a significant risk to user account integrity and system availability. Exploitation could lead to unauthorized deletion of user accounts or critical data, disrupting business operations, causing denial of service to legitimate users, and potentially enabling privilege escalation or further attacks. Given that ERP systems often contain sensitive business and financial data, the improper authorization could indirectly affect confidentiality if attackers leverage deleted accounts to bypass controls or cause operational chaos. The medium severity rating reflects that while the vulnerability is not trivially exploitable by unauthenticated attackers, the requirement for limited privileges means insider threats or compromised accounts could be leveraged to cause damage. European organizations relying on jshERP for critical enterprise resource planning functions may face operational disruptions, compliance risks under GDPR if personal data is affected, and reputational damage if the vulnerability is exploited. The public disclosure increases the urgency for mitigation to prevent exploitation by opportunistic attackers.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Aug 2025, 10:03 UTC

Technical details

References

Community reviews

Related threats