CVE-2025-15119VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15119: JeecgBoot · Improper Authorization

Affects JeecgBootSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

2.3Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% 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 28 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.

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
Mavenorg.jeecg/jeecgboot`pkg:maven/org.jeecg/jeecgboot`Other threats	Affected =3.0 =3.1 =3.2 =3.3 =3.4 =3.5 =3.6 =3.7 =3.8 =3.9.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Implement strict server-side authorization checks on the deptId parameter and all related API endpoints to ensure users can only access data within their authorized scope. 2. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to manipulate deptId or access /sys/sysDepartRole/list. 3. Monitor logs for unusual access patterns or repeated failed authorization attempts targeting the vulnerable endpoint. 4. Restrict access to the affected API endpoint to trusted networks or VPNs where possible to reduce exposure. 5. Conduct internal code reviews and security testing to identify and remediate similar authorization issues in customizations or integrations. 6. Engage with the JeecgBoot community or maintainers for updates or unofficial patches and consider contributing fixes if feasible. 7. Isolate sensitive data and apply the principle of least privilege in role assignments to limit potential data exposure. 8. Prepare incident response plans to quickly address any detected exploitation attempts. 9. If feasible, consider migrating to alternative platforms or versions not affected by this vulnerability until an official patch is released.

Description

A vulnerability was detected in JeecgBoot up to 3.9.0. This issue affects the function queryPageList of the file /sys/sysDepartRole/list. The manipulation of the argument deptId results in improper authorization. The attack can be executed remotely. A high complexity level is associated with this attack. The exploitability is assessed as difficult. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using JeecgBoot in their enterprise environments, this vulnerability could result in unauthorized access to internal role and department-related data, potentially exposing sensitive organizational structures or user-role mappings. While the impact on confidentiality is limited (low confidentiality impact), unauthorized data access could facilitate further reconnaissance or privilege escalation attempts if combined with other vulnerabilities. The difficulty of exploitation and requirement for low-level privileges reduce the likelihood of widespread exploitation, but targeted attacks against organizations with sensitive data or critical infrastructure could still pose a risk. The absence of vendor patches means organizations must rely on compensating controls, increasing operational risk. Data privacy regulations such as GDPR may be implicated if unauthorized access leads to exposure of personal data, potentially resulting in regulatory penalties. The threat is more relevant to organizations with internal deployments of JeecgBoot, especially those integrating it into HR, access control, or internal management systems.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 23:14 UTC

Technical details

References

Community reviews

Related threats