CVE-2026-65688: Bold Reports Standalone Report Designer < 14.1.12 Arbitrary File Read via Font Processing
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.
Security readout for executives and security teams
Plain-English summary
An unauthenticated remote attacker can abuse font processing in the DataHub module to read files from the report server. Exposed files may contain authentication credentials, potentially allowing complete unauthorized application access. Products before DataHub's introduction in version 6.3 are not affected.
Executive priority
Treat reachable affected deployments as an immediate remediation priority because exploitation requires no authentication and may expose credentials. Prioritize internet-facing systems, upgrade promptly, restrict access during remediation, and initiate credential review where compromise cannot be excluded.
Technical view
CVE-2026-65688 is a CWE-22 path-traversal flaw caused by missing filepath validation in Bold Reports Standalone Report Designer DataHub font processing. A crafted network request can disclose arbitrary server files without privileges or user interaction. The supplied CVSS 3.1 score is 9.8.
Likely exposure
Highest risk applies to network-accessible Standalone Report Designer deployments running DataHub from version 6.3 to a release before 14.1.12. Exposure depends on whether attackers can reach the vulnerable font-processing functionality. Versions before 6.3 are explicitly described as unaffected.
Exploitation context
The weakness is remotely reachable, low complexity, unauthenticated, and requires no user interaction. Disclosed credentials could enable broader application compromise. The supplied record is not marked as CISA KEV, and the sources provided do not establish active exploitation.
Researcher notes
The supplied affected-version list includes 14.1.12, but the title and description state that versions before 14.1.12 are vulnerable, implying 14.1.12 contains the fix. Confirm exact version boundaries against vendor guidance. No exploit activity is established by the supplied evidence.
Mitigation direction
Upgrade affected installations to version 14.1.12 or later after confirming current vendor guidance.
Restrict external access to DataHub until affected systems are upgraded.
Rotate credentials potentially stored on exposed servers after assessing possible file disclosure.
Review vendor release notes for deployment-specific remediation requirements.
Validation and detection
Inventory Standalone Report Designer versions and identify deployments using the DataHub module.
Confirm externally reachable systems cannot access vulnerable font-processing functionality without authorization.
Verify upgraded systems report version 14.1.12 or later.
Review application and access logs for unusual font-processing requests or sensitive-file access.
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.
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.
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory
Improper Limitation of a Pathname to a Restricted Directory represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.