Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-75479 – Authentication Bypass / Sensitive Data Exposure – JimuReport ≤ 2.3.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-75479 is an authentication bypass (CWE-306, Missing Authentication for Critical Function) in JimuReport, an open-source Java reporting/BI tool from jeecgboot. The report folder template listing endpoint can be queried by unauthenticated attackers to enumerate all reports and harvest embedded share tokens, which can then be replayed against protected report endpoints to retrieve full report definitions, SQL statements, and live query results. The flaw affects JimuReport versions 0 through 2.3.4 and carries a HIGH severity rating.

Technical details

  • Root cause: the endpoint GET /jmreport/query/report/folder/template is annotated @JimuNoLoginRequired, causing JimuReport’s token interceptor to skip authentication validation for it entirely.
  • Trigger condition: an attacker simply sends an unauthenticated HTTP request to the exposed endpoint on an internet-facing JimuReport instance.
  • Attack vector: network, no authentication or user interaction required, low attack complexity.
  • Impact: the response discloses report metadata and shareViewUrl values containing share tokens. Those tokens can be reused against other share-accessible endpoints (e.g. /jmreport/show, /jmreport/getCharData) to retrieve complete report definitions, including embedded SQL statements and live query data — resulting in high-confidentiality information disclosure without requiring credentials.

Affected software

  • JimuReport (jeecgboot/jimureport), versions 0 through 2.3.4 (confirmed vulnerable at commit fdd1ad4).

Severity

  • CVSS v3.1: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CVSS v4.0: 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

Mitigation and recommended actions

  • Immediate: no patched JimuReport version has been published by the vendor as of this writing; monitor the vendor’s GitHub repository and issue tracker for a fix and upgrade as soon as one is released.
  • Workarounds: restrict network exposure of JimuReport to trusted internal networks or VPNs rather than the public internet; place the application behind a reverse proxy or WAF that blocks unauthenticated requests to /jmreport/query/report/folder/template and other /jmreport/* share-related endpoints; rotate/invalidate any share tokens that may have been exposed; monitor access logs for enumeration attempts against the report folder template listing endpoint.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge