dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7182

CRITICAL · 9.2 CVSS v4.0 Published 2026-05-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Diagram's export module is vulnerable to Path Traversal in src attribute 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 version 1.1.1.

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

Path traversal vulnerability in Diagram's export module allows unauthenticated attackers to include local server files in PDF output by crafting malicious HTML payloads in the src attribute without proper sanitization.

MitigationUpgrade to version 1.1.1 which contains the fix, or implement robust HTML sanitization on the src attribute in the export module to prevent path traversal attacks.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Diagram application installation
    Locate the Diagram application on the server by searching for files named 'diagram', 'export', or checking common web application directories for Diagram-related components
    Affected if The Diagram application or its export module is present on the system
  2. Determine installed version
    Check version files, application metadata, or the binary/library version of the Diagram component. Common locations include version.txt, about page, or using a version command specific to the application
    Affected if The version is below 1.1.1 (the fixed release)
  3. Verify export module is enabled
    Inspect the application configuration or module settings to confirm whether the Diagram export module (PDF export functionality) is currently enabled and accessible
    Affected if The export module is enabled and accessible to users
  4. Check for HTML sanitization on src attribute
    Examine the export module source code or configuration files for how the src attribute is handled. Look for HTML sanitization, input validation, or path validation logic around the export functionality
    Affected if No sanitization or path validation is implemented on the src attribute in the export module
  5. Review access controls on export endpoint
    Check if the export endpoint requires authentication or is exposed to unauthenticated users. Inspect web server configuration or application routing for the export module paths
    Affected if The export endpoint is accessible without authentication

A user is affected if they have the Diagram export module enabled, running a version prior to 1.1.1, with the export functionality exposed to users without proper HTML sanitization on the src attribute.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.1.1 which contains the fix, or implement robust HTML sanitization on the src attribute in the export module to prevent path traversal attacks.

Recommended fix Moderate confidence

dhtmlx Diagram version 1.1.1

  1. Identify the dhtmlx Diagram library version currently in use in your project
  2. Locate the package.json, bower.json, or other dependency management files to confirm the current version
  3. Upgrade the dhtmlx Diagram package to version 1.1.1 or later
  4. Run package manager update command (e.g., npm update, yarn upgrade, or composer update depending on your setup)
  5. Verify the upgrade was successful by checking the installed version
  6. Test the Diagram export functionality to ensure the path traversal vulnerability is resolved
  7. Rebuild and redeploy your application with the patched library

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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