# CVE-2025-14908: JeecgBoot Multi-Tenant Management SysTenantController.java improper authentication

> Remote attackers can bypass authentication in the Multi-Tenant Management Module by manipulating the ID argument, potentially gaining unauthorized access.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-q9f7-mpvw-2h86

## What is CVE-2025-14908?

CVE-2025-14908 is a medium-severity authentication bypass vulnerability in Jeecg Jeecg Boot, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2025-14908?

It affects 1 product.


Products: Jeecg Jeecg Boot.

## How do I fix CVE-2025-14908?

No fix has been published for CVE-2025-14908 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14908 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14908 exists.

## Other vulnerabilities in Jeecg Jeecg Boot

- [CVE-2024-40489](https://insights.sbomify.com/CVE-2024-40489/): Code injection in n/a (critical 9.8)
- [CVE-2024-43028](https://insights.sbomify.com/CVE-2024-43028/): Command injection in n/a (critical 9.8)
- [CVE-2024-48307](https://insights.sbomify.com/CVE-2024-48307/): JeecgBoot SQL Injection vulnerability (critical 9.8)
- [CVE-2023-41542](https://insights.sbomify.com/CVE-2023-41542/): Jeecg Boot SQL injection vulnerability (critical 9.8)
- [CVE-2023-41543](https://insights.sbomify.com/CVE-2023-41543/): Jeecg Boot SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14908 and fix it if it is affected.

What it is: CVE-2025-14908 is a medium-severity authentication bypass vulnerability in Jeecg Jeecg Boot, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14908 exists.

Affected product: Jeecg Jeecg Boot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14908/ (Markdown: https://insights.sbomify.com/CVE-2025-14908/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14908
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14908
- OSV: https://osv.dev/vulnerability/CVE-2025-14908

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14908/
Summaries are generated and may contain mistakes; the official description above is the record.