CVE-2025-10976VulnerabilityPublished 25 Sep 2025

CVE-2025-10976: JeecgBoot · Improper Authorization

Affects JeecgBootSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
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: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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 25 Sep 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-26.

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 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
JeecgBoot	Affected =3.8.0 =3.8.1 =3.8.2	Fixed in–

AI-suggested

1. Immediate mitigation should include restricting external access to the /api/getDepartUserList endpoint via network controls such as firewalls or API gateways to limit exposure. 2. Implement additional authorization checks at the application level to validate 'departId' parameters against the authenticated user's permissions, ensuring users can only query data for departments they are authorized to access. 3. Monitor logs for unusual or unauthorized access patterns to this API endpoint to detect potential exploitation attempts. 4. If possible, upgrade to a patched version once the vendor releases one; until then, consider applying custom patches or workarounds to enforce proper authorization. 5. Conduct a thorough inventory of all JeecgBoot instances in the environment to identify and prioritize remediation. 6. Educate developers and security teams on secure API design principles to prevent similar authorization issues in future development. 7. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious manipulation of the 'departId' parameter. These targeted measures go beyond generic advice by focusing on access control enforcement, monitoring, and network-level protections specific to this vulnerability.

Description

A vulnerability was determined in JeecgBoot up to 3.8.2. This issue affects some unknown processing of the file /api/getDepartUserList. Executing manipulation of the argument departId can lead to improper authorization. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using JeecgBoot versions 3.8.0 through 3.8.2, this vulnerability could lead to unauthorized disclosure of internal department user information. While the impact is limited to confidentiality and the severity is low, exposure of such data could facilitate further targeted attacks such as social engineering or insider threat activities. Organizations in regulated sectors (e.g., finance, healthcare, public sector) may face compliance risks if sensitive user data is exposed. However, the high complexity and difficulty in exploitation reduce the likelihood of widespread exploitation. The lack of vendor response and patch availability means organizations must proactively assess and mitigate the risk. Given the remote exploitability without authentication, any publicly accessible instances of JeecgBoot with the affected versions are at risk. Overall, the impact is moderate for European enterprises relying on this platform, especially those with sensitive internal user data and regulatory obligations.

Summary

CVE-2025-10976 is a security vulnerability identified in JeecgBoot versions up to 3.8.2. JeecgBoot is a rapid development platform often used for enterprise applications. The vulnerability arises from improper authorization checks in the processing of the API endpoint /api/getDepartUserList. Specifically, manipulation of the 'departId' parameter can bypass intended access controls, potentially allowing unauthorized users to access or retrieve data related to department user lists. The vulnerability can be exploited remotely without requiring user interaction or authentication, but the attack complexity is high, and exploitability is difficult. The CVSS 4.0 base score is 2.3 (low severity), reflecting limited impact and high attack complexity. The vendor has been contacted but has not responded or issued a patch, and no known exploits are currently observed in the wild. The vulnerability primarily impacts confidentiality due to unauthorized data access, with no direct impact on integrity or availability. The lack of authentication requirement increases the theoretical attack surface, but the high complexity and limited impact reduce the overall risk. This vulnerability highlights the importance of robust authorization checks on API endpoints handling sensitive parameters to prevent unauthorized data disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Oct 2025, 00:41 UTC

Technical details

References

Community reviews

Related threats