dbcve.org
Standalone Report DesignerApplication · Syncfusion

CVE-2026-65688

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-23
Fix available
A fix is available. Upgrade to 14.1.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 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
Bold Reports Standalone Report Designer before 14.1.12 contains a missing filepath validation vulnerability in its font processing feature that allows unauthenticated attackers to read arbitrary files from the server filesystem by supplying a crafted request. Attackers can exploit this path traversal weakness to disclose sensitive server files, including authentication credentials, enabling full unauthorized access to the application. The vulnerability is specific to the DataHub module, which was introduced in Bold Reports 6.3. Therefore, versions prior to 6.3 are not affected.

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

A path traversal vulnerability in Bold Reports Standalone Report Designer's font processing feature within the DataHub module allows unauthenticated attackers to read arbitrary files from the server filesystem by supplying crafted requests with manipulated file paths. Attackers can exploit this to disclose sensitive files including authentication credentials.

MitigationUpgrade Bold Reports to version 14.1.12 or later which implements proper filepath validation in the font processing feature. Alternatively, disable or restrict access to the DataHub module if upgrading is not immediately feasible.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Standalone Report DesignerApplication
Affected:>= 6.3, < 14.1.12

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
High
Availability
High

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

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. Identify if Bold Reports or Syncfusion Report Designer is installed
    Locate the installation directory or check installed programs list. Look for 'Bold Reports', 'Bold Reports Designer', or legacy 'Syncfusion Report Designer' entries.
    Affected if The software is present on the system
  2. Determine the installed version number
    Check the application's About section, readme file, or version metadata within the installation directory. Compare the version to the affected range: versions 6.3 through 14.1.11 are vulnerable.
    Affected if The installed version is >= 6.3 and < 14.1.12
  3. Verify if the DataHub module is accessible
    Attempt to access the DataHub endpoint via HTTP/HTTPS request, or check the application's module configuration to confirm DataHub is enabled and exposed.
    Affected if DataHub module is enabled and network-accessible
  4. Review web server or application logs for path traversal patterns
    Examine access logs for the DataHub font processing endpoints, searching for sequences like '../', '..\', or absolute path patterns in font-related requests.
    Affected if Log entries show anomalous font requests with traversal sequences targeting sensitive paths

A system is affected if Bold Reports or Syncfusion Report Designer version 6.3 through 14.1.11 is installed with the DataHub module enabled and accessible.

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
Upgrade available Upgrade to 14.1.12 or later
Fixed in 14.1.12
Interim mitigation

Upgrade Bold Reports to version 14.1.12 or later which implements proper filepath validation in the font processing feature. Alternatively, disable or restrict access to the DataHub module if upgrading is not immediately feasible.

Recommended fix High confidence

14.1.12

  1. 1. Identify the current version of Bold Reports Standalone Report Designer installed on the server
  2. 2. Navigate to the Bold Reports official download or customer portal
  3. 3. Download Bold Reports Standalone Report Designer version 14.1.12 or later
  4. 4. Back up the existing Bold Reports installation and its configuration files
  5. 5. Stop the Bold Reports services running on the server
  6. 6. Install the upgraded version (14.1.12 or newer) following the standard upgrade procedure
  7. 7. Restore the configuration from the backup if needed
  8. 8. Restart the Bold Reports services

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

Fix this in Standalone Report Designer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-65688 — 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-65688 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