CVE-2026-41552
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 · uneditedPDF Export Module used in DHTMLX's products Gantt and Scheduler is vulnerable to Path Traversal due to lack of HTML sanitization. An unauthenticated user could craft the html payload which could include local files from the server and display them in the generated PDF. This issue was fixed in PDF Export Module version 0.7.6.
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 confidenceThe PDF Export Module in DHTMLX Gantt and Scheduler products lacks HTML sanitization, enabling a Path Traversal attack. An unauthenticated attacker can craft malicious HTML payloads containing path traversal sequences (e.g., ../../etc/passwd) to access local server files and embed their contents into generated PDF documents.
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>= 0.3.3, < 0.7.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify DHTMLX installationSearch for DHTMLX Gantt or Scheduler libraries in your web application directory (typically in /js/, /lib/, or /components/ folders). Look for files named gantt.js, scheduler.js, or dhtmlx.*.jsAffected if DHTMLX Gantt or Scheduler libraries are present in the application
-
Locate PDF Export Module versionFind the PDF export module file (commonly named dhtmlxgantt_pdf.js, pdf.js, or similar within the ext/ or related folders). Open the file and search for a version string or version number declaration in the header comments or codeAffected if The PDF export module version is found to be 0.3.3 or higher but below 0.7.6
-
Check if PDF export is configuredReview your application JavaScript initialization code for Gantt or Scheduler. Look for calls to enablePDFExport(), gantt.config.pdf_export = true, or similar configuration flags that enable the PDF export functionalityAffected if PDF export is explicitly enabled in the application configuration
-
Inspect web server access logsReview web server access logs (Apache access.log, Nginx access.log, or IIS logs) for requests to the PDF export endpoint containing path traversal patterns. Search for sequences like ../, ..\, or /etc/passwd in URL parameters
A user is affected if DHTMLX Gantt or Scheduler with the PDF Export Module version between 0.3.3 and 0.7.6 is deployed and the PDF export feature is enabled in their application.
Generated from the published advisory. Verify against your own configuration.
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 · scoped0.7.6
Upgrade the PDF Export Module to version 0.7.6 or later. If immediate upgrading is not feasible, implement strict input validation to sanitize HTML content and block path traversal sequences before PDF generation.
Pdf Export Module version 0.7.6
- Identify the Pdf Export Module dependency in your project (likely via package.json, composer.json, or similar dependency file)
- Update the pdf-export-module package version to 0.7.6 or later
- Run package manager update command (e.g., npm update, composer update) to install the fixed version
- Verify the new version is installed correctly by checking your dependency lock file
- Test the PDF export functionality in your DHTMLX Gantt or Scheduler integration to confirm the fix works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41552 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41552 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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