dbcve.org
Pdf Export ModulePlugin / extension · Dhtmlx

CVE-2026-41553

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-15
Fix available
A fix is available. Upgrade to 0.7.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
PDF Export Module used in DHTMLX's products Gantt and Scheduler is vulnerable to Remote Code Execution due to lack of "data" parameter sanitization. An unauthenticated attacker can inject the malicious JavaScript code to the parameter whose value is processed by Node.js and subsequently executed. This can lead to server compromise. 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 confidence

The PDF Export Module in DHTMLX's Gantt and Scheduler products lacks sanitization on the 'data' parameter, allowing unauthenticated attackers to inject arbitrary JavaScript code that is processed and executed by the Node.js backend, leading to complete server compromise.

MitigationUpgrade the PDF Export Module to version 0.7.6 or later to remediate this RCE vulnerability.

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
Pdf Export ModulePlugin / extension
Affected:< 0.7.6

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Locate the DHTMLX PDF Export Module installation
    Search for the dhtmlx-pdf-export or similar package in your project's node_modules directory, or check your package.json dependencies for any dhtmlx-related packages with pdf export functionality
    Affected if The dhtmlx pdf export module is present in the application dependencies
  2. Identify the installed PDF Export Module version
    Check the package.json file for the exact version number of the dhtmlx pdf export module, or run 'npm list dhtmlx-pdf-export' (or the specific package name) to see the installed version
    Affected if The installed version is lower than 0.7.6 or the version cannot be determined (indicating an old vulnerable release)
  3. Verify the Node.js backend processes PDF export requests
    Inspect your server configuration and routes to confirm the PDF export endpoint exists and is accessible. Look for route handlers that accept a 'data' parameter for PDF generation
    Affected if The PDF export endpoint is exposed and accepts a 'data' parameter from user input
  4. Check if unauthenticated access to PDF export is possible
    Review your authentication/authorization middleware on the PDF export route to determine if the endpoint requires authentication before processing the 'data' parameter
    Affected if The PDF export endpoint does not require authentication and processes user-supplied 'data' input

The environment is affected if the DHTMLX PDF Export Module version is below 0.7.6 AND the PDF export endpoint with the 'data' parameter is accessible without authentication.

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 0.7.6 or later
Fixed in 0.7.6
Interim mitigation

Upgrade the PDF Export Module to version 0.7.6 or later to remediate this RCE vulnerability.

Recommended fix High confidence

PDF Export Module version 0.7.6

  1. Verify the current version of the PDF Export Module in use by checking package.json or the installed module version
  2. Update the package.json dependency to specify version 0.7.6 of the PDF Export Module (e.g., dhtmlx-gantt-pdf or dhtmlx-scheduler-pdf, depending on product)
  3. Run 'npm install' or 'yarn install' to fetch and install the updated module version
  4. Verify that version 0.7.6 is now installed by checking the package-lock.json or running a version command
  5. Test the PDF export functionality in the DHTMLX Gantt or Scheduler application to ensure the upgrade does not break existing functionality
  6. If using a build system, rebuild the application to ensure the updated module is bundled correctly

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

Fix this in Pdf Export Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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