Which versions of JimuReport are affected by CVE-2026-75479?

JimuReport installations exposed to untrusted networks are vulnerable to CVE-2026-75479, which permits unauthenticated disclosure of sensitive report definitions, embedded SQL statements, and…

How to fix or mitigate CVE-2026-75479?

Within 24 hours, conduct an inventory of all JimuReport deployments and identify any instances reachable from the internet or untrusted networks, immediately implementing firewall rules to restrict access to the vulnerable endpoint. Over the next 7 days, deploy Web Application Firewall (WAF) rules to block requests to the report folder template listing endpoint, implement authentication proxies in front of all JimuReport instances, and review access logs for evidence of prior exploitation. Within 30 days, monitor vendor advisories for security patches; if no patch is released by the vendor, develop a comprehensive migration plan to either replace JimuReport or deploy it exclusively within internal, air-gapped networks with strict access controls, and assess any sensitive data exposed including embedded SQL statements and authentication tokens.

JimuReport CVE-2026-75479

Q: What is the CVSS score of CVE-2026-75479?

CVE-2026-75479 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.4%.

EUVD-2026-60391 HIGH

Missing Authentication for Critical Function (CWE-306)

2026-08-17 VulnCheck

GHSA-gvmm-h58c-795c

Authentication Bypass Jimureport Jeecgboot

8.7

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

7.5 HIGH

Network-accessible unauthenticated endpoint (PR:N, AV:N, AC:L); confidentiality-only impact (C:H) with no integrity or availability consequence and no scope change.

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 17, 2026 - 21:08 vuln.today

CVE Published

Aug 17, 2026 - 20:36 cve.org

HIGH 8.7

DescriptionCVE.org

JimuReport contains an authentication bypass vulnerability in the report folder template listing endpoint that allows unauthenticated attackers to enumerate all reports and retrieve share tokens. Attackers can use disclosed share tokens to access protected report endpoints and retrieve full report definitions including embedded SQL statements and live query data.

AnalysisAI

Unauthenticated access to JimuReport's report folder template listing endpoint exposes all report definitions, share tokens, embedded SQL statements, and live query data to any remote attacker. The CWE-306 root cause - missing authentication for a critical function - means the disclosure requires no credentials, no user interaction, and no special tooling. With a CVSS 4.0 score of 8.7 and a network-accessible, zero-complexity attack path, this represents a high-priority information disclosure risk for any JimuReport deployment reachable from an untrusted network. No public exploit or CISA KEV listing has been identified at time of analysis, though the vulnerability is fully disclosed via VulnCheck advisory and a public GitHub issue.

Technical ContextAI

JimuReport is an open-source drag-and-drop reporting and data visualization tool developed under the jeecgboot project (CPE: cpe:2.3:a:jeecgboot:jimureport:*:*:*:*:*:*:*:*), commonly deployed as a Java web application. The vulnerable component is the report folder template listing endpoint, which is intended to display available report templates and associated metadata including share tokens. CWE-306 (Missing Authentication for Critical Function) describes the root cause precisely: a privileged function - one that exposes sensitive business intelligence artifacts - lacks any authentication gate. Because share tokens are returned alongside folder listings, an attacker who queries the unauthenticated endpoint obtains the secondary credential needed to access otherwise-protected report endpoints, creating a two-stage disclosure chain from a single unauthenticated request.

RemediationAI

No vendor-released patch has been identified at time of analysis; the vulnerability is disclosed via GitHub issue https://github.com/jeecgboot/jimureport/issues/4695, which should be monitored for an upstream fix. Until a patched release is available, operators should immediately restrict network access to the report folder template listing endpoint using a reverse proxy, WAF rule, or firewall ACL - blocking unauthenticated external requests to that specific endpoint path eliminates the primary attack surface with minimal functional impact on authenticated internal users. As a secondary control, rotate or invalidate all existing share tokens to limit value of any tokens already disclosed. If the reporting application must remain internet-facing, consider placing it behind authentication middleware (e.g., an SSO proxy) at the network perimeter. Disabling the share token feature entirely, if the JimuReport configuration supports it, removes the second-stage disclosure path. Consult the VulnCheck advisory at https://www.vulncheck.com/advisories/jimureport-unauthenticated-report-listing-and-share-token-disclosure for updates on patch availability.