Summary
JimuReport contains an authentication bypass in its report folder template listing endpoint. An unauthenticated attacker may enumerate reports, obtain share tokens, and use them to access protected report data, including report definitions, embedded SQL statements, and live query results.
Affected context
The vulnerability occurs in JimuReport deployments where the report folder template listing endpoint is reachable without effective authentication enforcement. Risk increases when report metadata or share tokens are returned to unauthenticated users and those tokens grant access to protected report endpoints or live query results.
Exploit preconditions
- Attack surface: The report folder template listing endpoint and related report-sharing endpoints
- Required access: Network access to the exposed JimuReport service; valid authentication may not be required for the initial listing request
- Trigger point: Requesting report folder or template listings and processing disclosed share tokens
- Why exploitation is possible: The endpoint does not consistently enforce authentication before exposing report identifiers or access tokens
Why this happens
The underlying issue is an authentication enforcement failure mapped to CWE-306: Missing Authentication for Critical Function. A sensitive report-listing operation is exposed without reliably verifying the caller's identity and authorization, allowing unauthenticated requests to obtain information that can be used to reach protected report resources. Returning reusable share tokens further weakens the trust boundary between public listing functionality and restricted report access.
Potential impact
- An attacker may enumerate report templates and report metadata
- Disclosed share tokens could enable unauthorized access to protected reports
- Report definitions containing embedded SQL statements may be exposed
- Live query data could be retrieved without the intended authorization
- Sensitive business information may be disclosed or used to support further attacks
General mitigation guidance
Mitigation generally focuses on enforcing authentication and authorization consistently across report discovery, token issuance, and report retrieval paths.
Common defensive patterns include:
- Require authentication before processing report-listing and template-enumeration requests
- Apply server-side authorization checks for every report and folder access
- Avoid exposing reusable share tokens through unauthenticated responses
- Use narrowly scoped, time-limited access tokens when sharing is required
- Reduce sensitive data returned by listing endpoints to the minimum necessary
- Apply least privilege to report service accounts and data-source credentials
- Treat embedded SQL and live query results as sensitive information
How teams detect issues like this
Organizations can assess for this class of issue through:
- Dynamic tests that request report-listing endpoints without credentials and verify that sensitive metadata is not returned
- Authorization tests covering anonymous, authenticated, and cross-tenant access scenarios
- Static analysis and code review for missing authentication middleware on sensitive routes
- Review of token-generation and token-validation paths for predictable, reusable, or overly broad access grants
- API gateway policies requiring authentication for report and template endpoints
- Monitoring for anonymous enumeration, unusual report-listing volume, and token use from unexpected clients
Automated security testing and code review tools may help identify inconsistent access-control enforcement.

