dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-58375

HIGH · 7.5 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
JimuReport through 2.5.0 exposes the POST /jmreport/auto/export endpoint without authentication: the handler is annotated @JimuNoLoginRequired, so JimuReportTokenInterceptor skips all authentication and authorization, and the export service streams the rendered report for any supplied report id without verifying the auto-export configuration flag. An unauthenticated remote attacker can enumerate Snowflake report identifiers and export the full contents of any report, including the data returned by the report configured SQL queries and any credentials embedded in its data sources.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

JimuReport through 2.5.0 has an unauthenticated API endpoint (POST /jmreport/auto/export) that lacks proper authorization checks due to the @JimuNoLoginRequired annotation causing the interceptor to skip authentication. The export functionality also fails to validate the auto-export configuration flag, allowing any report to be exported without credentials.

MitigationAdd authentication/authorization checks to the /jmreport/auto/export endpoint or remove the @JimuNoLoginRequired annotation, and ensure the export service validates the auto-export configuration flag before allowing exports.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate JimuReport installation
    Search for jimureport JAR/WAR files in the application deployment directory, or check the application's pom.xml/build.gradle for jimureport dependency, or look for jimureport-related JARs in the lib/classpath
    Affected if JimuReport library or application is found in the environment
  2. Determine installed JimuReport version
    Check the version of the jimureport JAR/WAR file name, or look at the pom.xml/build.gradle dependency version, or inspect the JAR manifest file for the version attribute
    Affected if Version is 2.5.0 or any earlier version (e.g., 2.4.x, 2.3.x, etc.)
  3. Verify vulnerable endpoint is exposed
    Send a POST request to /jmreport/auto/export (or the equivalent path in your deployment) with a test report ID parameter and observe if the server returns exported report data without requiring authentication
    Affected if The endpoint responds with report export data without any login or session validation
  4. Check interceptor configuration
    Inspect the application source code or configuration for JimuReportTokenInterceptor to confirm it skips authentication for endpoints annotated with @JimuNoLoginRequired, or check if /jmreport/auto/export is in an allowed unauthenticated path list
    Affected if The interceptor explicitly bypasses authentication for the /jmreport/auto/export endpoint

The environment is affected if JimuReport version 2.5.0 or earlier is installed AND the /jmreport/auto/export endpoint is accessible without authentication, allowing unauthenticated export of any report.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add authentication/authorization checks to the /jmreport/auto/export endpoint or remove the @JimuNoLoginRequired annotation, and ensure the export service validates the auto-export configuration flag before allowing exports.

Recommended fix Moderate confidence

JimuReport version > 2.5.0 (e.g., 2.5.1 or latest stable)

  1. Check the official JimuReport GitHub releases page (github.com/jeecgboot/JimuReport) for versions after 2.5.0 to identify the version that addresses CVE-2026-58375
  2. If a specific fixed version is not clearly documented, upgrade to the latest stable release of JimuReport
  3. After upgrading, verify that the /jmreport/auto/export endpoint now requires authentication
  4. Confirm that the @JimuNoLoginRequired annotation is removed from the export handler or that proper authentication checks are in place
Caveat Review release notes for any breaking changes between 2.5.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58375 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-58375 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data