dbcve.org
Jeecg BootApplication · Jeecg

CVE-2025-10319

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to after 3.8.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in JeecgBoot up to 3.8.2. Affected by this issue is some unknown functionality of the file /sys/tenant/exportLog of the component Tenant Log Export. The manipulation results in improper authorization. The attack can be launched remotely. The exploit has been released to the public and may be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JeecgBoot up to v3.8.2 contains an improper authorization vulnerability in the Tenant Log Export functionality at /sys/tenant/exportLog. An authenticated attacker with lower privileges can potentially export tenant logs belonging to other tenants due to missing or insufficient authorization checks on this endpoint. The exploit is publicly available.

MitigationImplement proper authorization checks on the /sys/tenant/exportLog endpoint to verify the user has legitimate access to the tenant data being requested. Validate that the requesting user has permission to access the specific tenant logs before allowing the export operation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jeecg BootApplication
Affected:<= 3.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JeecgBoot version
    Check the application's version file or pom.xml for the Jeecg Boot version. Common locations: version in application.yml, pom.xml dependency version, or the login page footer displaying the version.
    Affected if The installed version is JeecgBoot <= 3.8.2.
  2. Verify multi-tenant configuration exists
    Examine the application's database or configuration for tenant-related tables (such as sys_tenant, sys_tenant_type, sys_tenant_share_scope) and settings in application.yml or database configuration.
    Affected if The application has multi-tenancy enabled (multiple tenants exist in sys_tenant table or tenant mode is configured).
  3. Confirm /sys/tenant/exportLog endpoint exists
    Check the application's routing configuration or Swagger/API documentation for the presence of the /sys/tenant/exportLog endpoint. Review the controller code for RequestMapping to /sys/tenant/exportLog.
    Affected if The endpoint /sys/tenant/exportLog is present in the application routing.
  4. Inspect authorization logic on exportLog endpoint
    Review the Java controller method handling /sys/tenant/exportLog for @PreAuthorize annotations or manual permission checks. Look for code that validates tenant_id or tenant_code parameters against the current user's tenant context.
    Affected if The endpoint lacks proper @PreAuthorize annotations or does not validate that the requesting user has permission to access the specified tenant's data.
  5. Test tenant boundary in exportLog functionality
    As a lower-privileged user belonging to Tenant A, attempt to call the /sys/tenant/exportLog endpoint with parameters referencing Tenant B's tenant ID. Observe whether the export succeeds and returns Tenant B's logs.
    Affected if A user from Tenant A can successfully export logs belonging to Tenant B without authorization error.

You are affected if your JeecgBoot version is 3.8.2 or lower, multi-tenancy is enabled, and the /sys/tenant/exportLog endpoint allows users to access data from tenants other than their own.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 3.8.2
Interim mitigation

Implement proper authorization checks on the /sys/tenant/exportLog endpoint to verify the user has legitimate access to the tenant data being requested. Validate that the requesting user has permission to access the specific tenant logs before allowing the export operation.

Fix this in Jeecg Boot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10319 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10319 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data