VulnerabilityPublished 28 Dec 2025Updated 29 Dec 2025

CVE-2025-15123: JeecgBoot · Improper Authorization

Affects JeecgBootSource CVE Database V5

Public exploit available · CVSS 2.3 Low.

Data as of 26 Oct 2026, 17:16 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 24% 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: 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
Mavenorg.jeecg/jeecgboot`pkg:maven/org.jeecg/jeecgboot`Other threats	Affected 3.0 – 3.9.0 10 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

European organizations should immediately audit and tighten access controls around the /sys/sysDepartPermission/datarule/ functionality in JeecgBoot. Implement network-level restrictions to limit access to the affected endpoints only to trusted internal users or systems. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting authorization manipulation. Monitor logs for unusual access patterns or failed authorization attempts related to this endpoint. If feasible, isolate or sandbox the affected components to reduce potential impact. Engage in active threat hunting to detect any attempts to exploit this vulnerability. Maintain up-to-date backups and prepare incident response plans in case exploitation occurs. Finally, keep abreast of any vendor updates or community patches.

Description

A vulnerability was determined in JeecgBoot up to 3.9.0. This affects an unknown function of the file /sys/sysDepartPermission/datarule/. Executing manipulation can lead to improper authorization. It is possible to launch the attack remotely. The attack requires a high level of complexity. The exploitability is reported 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, this vulnerability could lead to unauthorized access or modification of department permission data, potentially allowing privilege escalation or unauthorized data access within the application. However, the low severity and high complexity reduce the likelihood of widespread exploitation. Organizations in sectors with sensitive internal data or strict compliance requirements (e.g., finance, healthcare, government) could face risks if attackers leverage this flaw to bypass internal access controls. The lack of vendor response and patch increases the risk window, especially for organizations that have not implemented compensating controls. The impact on confidentiality, integrity, and availability is limited but could still undermine trust in internal access management and lead to compliance issues under regulations such as GDPR if unauthorized data access occurs.

Summary

CVE-2025-15123 is a security vulnerability identified in JeecgBoot, an open-source rapid development platform, affecting all versions up to 3.9.0. The vulnerability resides in an unspecified function within the /sys/sysDepartPermission/datarule/ path, which handles authorization rules related to system department permissions. Due to improper authorization checks, an attacker with some level of privileges (low privileges required) can remotely manipulate authorization data, potentially bypassing intended access controls. The attack vector is network-based with no user interaction needed, but the attack complexity is high, indicating that exploitation requires detailed knowledge of the system and careful crafting of requests. The CVSS 4.0 base score is 2.3, reflecting low severity due to limited impact on confidentiality, integrity, and availability, and the requirement for some privileges. The vendor was notified but has not responded or issued a patch, and no known exploits are currently active in the wild. The vulnerability could allow unauthorized access to certain data or functions if exploited, but the scope and impact are limited by the complexity and privilege requirements.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats