ReaderApplication · Foxitsoftware

CVE-2020-8845

HIGH · 7.8 CVSS v3.1 Published 2020-02-14
Fix available
A fix is available. Upgrade to after 9.7.0.29478 or later.
See remediation →
81/100
Remediation priority · High
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 atackers to execute arbitrary code on affected installations of Foxit PhantomPDF 9.6.0.25114. 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 handling of watermarks in AcroForms. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-9358.

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

A use-after-free or null pointer dereference vulnerability exists in Foxit PhantomPDF 9.6.0.25114 where the application fails to validate object existence before performing operations on watermarks in AcroForms. This allows remote attackers to execute arbitrary code via malicious PDF files or web pages requiring user interaction.

MitigationApply vendor-supplied patch for Foxit PhantomPDF. Until patched, exercise caution with untrusted PDF files and disable JavaScript execution in the PDF reader settings.

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

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify installed Foxit product
    Open Windows Control Panel > Programs and Features, or check C:\Program Files\Foxit Software or C:\Program Files (x86)\Foxit Software for Foxit Reader or PhantomPDF folders. Look for 'Foxit Reader' or 'Foxit PhantomPDF' in the program list.
    Affected if Either Foxit Reader or Foxit PhantomPDF is installed on the system
  2. Determine Foxit Reader version
    If Foxit Reader is installed, open the application, click Help > About Foxit Reader. The version number is displayed in the dialog (format: x.x.x.xxxxx).
    Affected if Version is 9.7.0.29478 or lower
  3. Determine Foxit PhantomPDF version
    If Foxit PhantomPDF is installed, open the application, click Help > About Foxit PhantomPDF. The version number is displayed in the dialog (format: x.x.x.xxxxx).
    Affected if Version is 9.7.0.29455 or lower
  4. Compare against affected version ranges
    Compare your recorded version number against the affected ranges: Reader <= 9.7.0.29478, PhantomPDF <= 9.7.0.29455. Note that minor version differences (like 9.7.0.29479 or 9.7.0.29456) are NOT affected.
    Affected if Installed version falls at or below the respective threshold for your product

If Foxit Reader version 9.7.0.29478 or lower, or Foxit PhantomPDF version 9.7.0.29455 or lower is installed, the environment is affected by this vulnerability.

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.0.29478
Interim mitigation

Apply vendor-supplied patch for Foxit PhantomPDF. Until patched, exercise caution with untrusted PDF files and disable JavaScript execution in the PDF reader settings.

Fix this in Reader Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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