Unauthenticated report access via leaked share tokens
Published Aug 17, 2026 · Updated Aug 18, 2026
Authentication bypass in JEECG JimuReport 2.3.4 and earlier allows remote attackers to read report metadata and share tokens via the folder template listing endpoint. In DesignReportController, GET /jmreport/query/report/folder/template is marked @JimuNoLoginRequired, and JimuReportTokenInterceptor.preHandle() returns before token validation, so the response exposes each report's shareViewUrl and embedded shareToken. Any network-reachable instance is exposed without credentials; replaying a leaked token against share-accessible endpoints such as /jmreport/show can disclose full report definitions, embedded SQL, and live query results.
Summary
What happened
Authentication bypass in JEECG JimuReport 2.3.4 and earlier allows remote attackers to read report metadata and share tokens via the folder template listing endpoint. In DesignReportController, GET /jmreport/query/report/folder/template is marked @JimuNoLoginRequired, and JimuReportTokenInterceptor.preHandle() returns before token validation, so the response exposes each report's shareViewUrl and embedded shareToken. Any network-reachable instance is exposed without credentials; replaying a leaked token against share-accessible endpoints such as /jmreport/show can disclose full report definitions, embedded SQL, and live query results.
The record
- CVE
- CVE-2026-75479
- Published
- Aug 17, 2026
- Updated
- Aug 18, 2026
- Vendor
- Beijing Guoju Information Technology Co., Ltd.
- Product
- JimuReport
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 17, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.3.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Issue #4695 PoC for unauthenticated report enumerationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo