CVE-2025-14908VulnerabilityPublished 19 Dec 2025

CVE-2025-14908: JeecgBoot · Improper Authentication

Affects JeecgBootSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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:L/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: Low
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: 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: 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 19 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. Immediately apply the official patch identified by commit hashes e1c8f00bf2a2e0edddbaa8119afe1dc92d9dc1d2 and 67795493bdc579e489d3ab12e52a1793c4f8a0ee to all affected JeecgBoot instances. 2. Restrict network access to the Multi-Tenant Management Module endpoints, ideally limiting exposure to trusted internal networks or VPNs. 3. Implement strict input validation and parameter sanitization on tenant management APIs to prevent manipulation of ID arguments. 4. Conduct thorough access control audits and review tenant management logs for suspicious activities indicating exploitation attempts. 5. Employ Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests targeting the vulnerable function. 6. Educate development and operations teams about the vulnerability and ensure secure coding practices for multi-tenant modules. 7. Monitor threat intelligence feeds for any emerging exploits or attack campaigns leveraging this vulnerability. 8. Consider additional segmentation of tenant data and services to limit lateral movement if compromise occurs. 9. Regularly update JeecgBoot and dependent components to the latest secure versions to mitigate future vulnerabilities.

Description

A security flaw has been discovered in JeecgBoot up to 3.9.0. The affected element is an unknown function of the file jeecg-boot/jeecg-module-system/jeecg-system-biz/src/main/java/org/jeecg/modules/system/controller/SysTenantController.java of the component Multi-Tenant Management Module. Performing manipulation of the argument ID results in improper authentication. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. The patch is named e1c8f00bf2a2e0edddbaa8119afe1dc92d9dc1d2/67795493bdc579e489d3ab12e52a1793c4f8a0ee. It is recommended to apply a patch to fix this issue.

Impact

For European organizations, this vulnerability poses a significant risk to multi-tenant applications built on or incorporating JeecgBoot up to version 3.9.0. Unauthorized access to tenant management could lead to data leakage between tenants, unauthorized modification of tenant configurations, or denial of service through tenant disruption. This is particularly critical for SaaS providers and enterprises managing sensitive or regulated data across multiple clients or departments. The remote exploitation capability without authentication increases the attack surface, especially for publicly accessible management interfaces. Confidentiality and integrity impacts are moderate but could escalate depending on the tenant data sensitivity. Availability could be affected if attackers disrupt tenant services. The medium CVSS score reflects these moderate but tangible risks. European organizations in sectors such as finance, healthcare, and public administration, which often use multi-tenant platforms, may face compliance and reputational risks if exploited. The absence of known active exploits currently provides a window for mitigation, but the public exploit release necessitates urgent patching and monitoring.

Summary

CVE-2025-14908 identifies an improper authentication vulnerability in JeecgBoot, an open-source rapid development platform widely used for enterprise applications. The flaw resides in the Multi-Tenant Management Module, specifically within the SysTenantController.java file. An attacker can remotely manipulate the ID argument in an unknown function to bypass authentication checks, effectively gaining unauthorized access to tenant management operations. This vulnerability affects all versions up to and including 3.9.0. The CVSS v4.0 base score is 5.3 (medium), reflecting network attack vector, low attack complexity, no required privileges or user interaction, but limited impact on confidentiality, integrity, and availability. The vulnerability does not require authentication or user interaction, making exploitation feasible remotely. Although no active exploits have been observed in the wild, a public exploit has been released, increasing the likelihood of exploitation attempts. The vendor has issued a patch identified by commit hashes e1c8f00bf2a2e0edddbaa8119afe1dc92d9dc1d2 and 67795493bdc579e489d3ab12e52a1793c4f8a0ee, which should be applied promptly. The vulnerability could allow attackers to manipulate tenant data or configurations, potentially leading to unauthorized data access or service disruption within multi-tenant environments. The lack of detailed CWE classification limits precise technical characterization, but the core issue is improper authentication due to insufficient validation of input parameters controlling access to tenant management functions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Dec 2025, 04:25 UTC

Technical details

References

Community reviews

Related threats