LiveActive security incident?Get immediate response
CVE Record

CVE-2026-65689: Bold Reports Standalone Report Designer < 14.1.12 Arbitrary File Read via Database Download

Bold Reports Standalone Report Designer before 14.1.12 contains a missing filepath validation vulnerability in its database download 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.

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

An internet-reachable reporting server could expose sensitive local files without requiring a login. Stolen configuration files or credentials may enable broader unauthorized application access. The issue affects the DataHub module introduced in version 6.3 and is fixed in version 14.1.12.

Executive priority

Treat internet-accessible or externally reachable affected systems as an immediate remediation priority. Upgrade promptly, restrict access during the remediation window, and investigate possible credential exposure. Internal-only systems still warrant urgent action because exploitation requires neither authentication nor user interaction.

Technical view

CVE-2026-65689 is a CWE-22 path traversal flaw in the Standalone Report Designer database download feature. Missing filepath validation allows unauthenticated, low-complexity requests to read arbitrary server files. Affected releases are DataHub-enabled versions from 6.3 through versions earlier than 14.1.12. CVSS 3.1 is 9.8.

Likely exposure

Exposure is most likely where Bold Reports Standalone Report Designer versions 6.3 through 14.1.11 use DataHub and the vulnerable download feature is network-accessible. Versions before 6.3 lack DataHub and are reported unaffected. The supplied evidence does not identify default deployment exposure.

Exploitation context

No CISA KEV listing or cited evidence of active exploitation is supplied. Exploitation is nevertheless described as unauthenticated, remote, and low complexity. Arbitrary file disclosure could expose credentials and enable subsequent unauthorized application access, but observed campaigns or public exploit availability are not established here.

Researcher notes

The supplied record attributes the flaw to missing filepath validation in DataHub's database download feature. The stated direct primitive is arbitrary file read; integrity and availability consequences depend on disclosed credentials enabling further access. Exact vulnerable endpoints, request patterns, and platform-specific file targets are not established by the supplied evidence.

Mitigation direction

  • Upgrade Bold Reports Standalone Report Designer to version 14.1.12 or later.
  • Restrict network access to the designer and DataHub until upgrading is complete.
  • Rotate credentials if sensitive configuration or authentication files may have been exposed.
  • Review current vendor guidance and release notes for additional remediation details.

Validation and detection

  • Inventory Standalone Report Designer versions and identify installations from 6.3 through 14.1.11.
  • Confirm whether DataHub and its database download feature are enabled and network-accessible.
  • Verify upgraded systems report version 14.1.12 or later.
  • Review application, proxy, and access logs for suspicious database download requests.
  • Assess whether exposed service credentials require rotation or broader incident investigation.
Prepared
Confidence
high
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-65689 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9VulnCheck
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-65689Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Bold Reports (By SyncFusion)Standalone Report Designer6.3, 7.1.10, 9.1, 10.1, 11.1, 12.1, 13.1, 14.1.12affected
Weakness

CWE details

CWE-22

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.