PhantompdfApplication · Foxitsoftware

CVE-2020-10892

HIGH · 8.8 CVSS v3.1 Published 2020-04-22
Fix available
A fix is available. Upgrade to after 9.7.1.29511 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PhantomPDF 9.7.0.29478. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the communication API. The issue lies in the handling of the CombineFiles command, which allows an arbitrary file write with attacker controlled data. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-9830.

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

Foxit PhantomPDF versions prior to the patch contain a vulnerability in the communication API's CombineFiles command. This command improperly handles file operations, allowing an attacker to write arbitrary files with attacker-controlled data. Successful exploitation enables remote code execution within the context of the current process.

MitigationApply the vendor-supplied patch by updating Foxit PhantomPDF to the latest version. Until patched, avoid opening untrusted PDF files or visiting untrusted web pages that could deliver malicious PDF content.

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
PhantompdfApplication
Affected:<= 9.7.1.29511
ReaderApplication
Affected:<= 9.7.1.29511

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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. Check if Foxit PhantomPDF or Reader is installed
    Look for Foxit software in the Windows Registry under HKLM\SOFTWARE\Foxit Software\ (or HKLM\SOFTWARE\WOW6432Node\ for 64-bit systems), or check for installation folders in Program Files or Program Files (x86).
    Affected if Foxit PhantomPDF or Reader is found on the system.
  2. Determine the installed version of Foxit PhantomPDF
    Query the registry key HKLM\SOFTWARE\Foxit Software\Foxit PhantomPDF\Install\Version or read the version info from the executable at the installation path (e.g., Foxit PhantomPDF.exe).
    Affected if The version returned is less than or equal to 9.7.1.29511.
  3. Determine the installed version of Foxit Reader
    Query the registry key HKLM\SOFTWARE\Foxit Software\Foxit Reader\Install\Version or read the version info from the executable at the installation path.
    Affected if The version returned is less than or equal to 9.7.1.29511.
  4. Verify the CombineFiles API functionality exists
    Check that the Foxit PhantomPDF or Reader installation includes the SDK or API components that support the CombineFiles command used in the communication API.
    Affected if The software includes the CombineFiles functionality and the version is within the affected range.

The system is affected if Foxit PhantomPDF or Reader version 9.7.1.29511 or lower is installed and the CombineFiles command is available in the communication API.

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.

From vendor data
Upgrade available Upgrade to a release after 9.7.1.29511
Interim mitigation

Apply the vendor-supplied patch by updating Foxit PhantomPDF to the latest version. Until patched, avoid opening untrusted PDF files or visiting untrusted web pages that could deliver malicious PDF content.

Fix this in Phantompdf 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 upgrade done

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-2020-10892 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-10892 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