dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-65108

CRITICAL · 10.0 CVSS v3.1 Published 2025-11-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
md-to-pdf is a CLI tool for converting Markdown files to PDF using Node.js and headless Chrome. Prior to version 5.2.5, a Markdown front-matter block that contains JavaScript delimiter causes the JS engine in gray-matter library to execute arbitrary code in the Markdown to PDF converter process of md-to-pdf library, resulting in remote code execution. This issue has been patched in version 5.2.5.

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 md-to-pdf library uses gray-matter to parse Markdown front-matter. By embedding JavaScript delimiters in the front-matter block, attackers can trigger arbitrary JavaScript execution in the md-to-pdf process, achieving remote code execution on the server. This is a critical injection vulnerability in the Markdown parsing stage.

MitigationUpgrade md-to-pdf to version 5.2.5 or later. Until patched, do not process untrusted Markdown files with md-to-pdf.

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
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. Identify md-to-pdf installation
    Check package.json for md-to-pdf dependency, or run 'npm list md-to-pdf' to list installed version
    Affected if md-to-pdf is present in dependencies and version is below 5.2.5
  2. Confirm gray-matter usage
    Inspect your project's node_modules/md-to-pdf or source code to verify it uses gray-matter for front-matter parsing
    Affected if gray-matter is used by md-to-pdf for parsing Markdown front-matter
  3. Determine Markdown processing context
    Review code that calls md-to-pdf conversion functions to identify what source files are processed
    Affected if md-to-pdf processes Markdown files that could contain untrusted front-matter content
  4. Check for user-supplied Markdown input
    Audit whether md-to-pdf receives input from untrusted sources (file uploads, API requests, external data)
    Affected if md-to-pdf processes Markdown content originating from users or untrusted sources
  5. Verify front-matter parsing is active
    Inspect the Markdown files or data processed to confirm they contain front-matter blocks (YAML between --- delimiters)
    Affected if Front-matter blocks are present in the Markdown files being processed by md-to-pdf

You are affected if md-to-pdf version is below 5.2.5 AND your application processes Markdown with front-matter from untrusted sources, allowing injection of JavaScript delimiters in the front-matter section.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade md-to-pdf to version 5.2.5 or later. Until patched, do not process untrusted Markdown files with md-to-pdf.

Recommended fix Moderate confidence

md-to-pdf version 5.2.5 or later

  1. 1. Identify the md-to-pdf package in your project dependencies (check package.json)
  2. 2. Run 'npm list md-to-pdf' to confirm the currently installed version
  3. 3. Run 'npm install [email protected]' to upgrade to the patched version
  4. 4. Verify the upgrade was successful by running 'npm list md-to-pdf'
  5. 5. Test your markdown to PDF conversion functionality to ensure the fix does not break existing workflows
  6. 6. If using as a dependency in another project, update the version in package.json and run 'npm update'
Caveat The gray-matter library behavior has changed; review any custom front-matter processing logic for compatibility

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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