# CVE-2026-58375: Jeecg JimuReport authentication bypass in report export endpoint

Source: https://junglewise.ai/threats/cve-2026-58375-jeecg-jimureport-authentication-bypass-in-report-export-endpoint  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-30. Updated: 2026-06-30  
License: CC BY 4.0 with a link back

CVE-2026-58375 · Severity: high · CVSS 7.5 · Published 2026-06-30

JimuReport, a data visualization and reporting tool, contains a security flaw that allows anyone on the network to download sensitive reports without logging in. By accessing a specific unprotected web address, an attacker can export full business reports, which may contain private customer data, financial records, or database credentials. This could lead to significant data breaches and the exposure of internal company information.

Vendors: [JeecgBoot](https://junglewise.ai/threats/vendors/jeecgboot).

## Quick answers

**Is CVE-2026-58375 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-58375 being exploited in the wild.

**How severe is CVE-2026-58375?** High severity, with a CVSS score of 7.5, published 30 June 2026.

**Which products and versions are affected?** JeecgBoot JimuReport through 2.5.0.

**Is there a fix for CVE-2026-58375?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-58375 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-58375?** Check whether you run JeecgBoot JimuReport at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A missing authentication vulnerability exists in JimuReport through version 2.5.0. The 'POST /jmreport/auto/export' endpoint is incorrectly annotated with '@JimuNoLoginRequired', causing the 'JimuReportTokenInterceptor' to bypass all authentication and authorization checks. Furthermore, the underlying service fails to verify the 'auto-export' configuration flag before processing requests. An unauthenticated remote attacker can exploit this by providing a targeted Snowflake report identifier to the endpoint, allowing them to download the rendered report in formats like Excel. This results in the unauthorized disclosure of SQL query results and potentially sensitive credentials stored within the report's data sources.

## Affected products

- jeecgboot JimuReport through 2.5.0

## Timeline

- 2026-06-03: disclosed: Vulnerability reported to vendor via email
- 2026-06-17: other: Public GitHub issue opened
- 2026-06-30: advisory: NVD and VulnCheck advisories published

## References

- [https://github.com/jeecgboot/jimureport/issues/4694](https://github.com/jeecgboot/jimureport/issues/4694)
- [https://www.vulncheck.com/advisories/jimureport-unauthenticated-report-export-via-jmreport-auto-export](https://www.vulncheck.com/advisories/jimureport-unauthenticated-report-export-via-jmreport-auto-export)

## Related threats

- [JeecgBoot JimuReport RCE via Aviator expression injection](https://junglewise.ai/threats/cve-2026-36418-jeecgboot-jimureport-rce-via-aviator-expression-injection)