Foxit ReaderApplication · Foxitsoftware

CVE-2021-27268

HIGH · 7.8 CVSS v3.1 Published 2021-03-30
Fix available
A fix is available. Upgrade to after 10.1.0.37527 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 attackers to execute arbitrary code on affected installations of Foxit PhantomPDF 10.1.0.37527. 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 U3D objects in PDF files. 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-12295.

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 in Foxit PhantomPDF's handling of U3D (3D) objects in PDF files allows remote attackers to execute arbitrary code via a specially crafted PDF that fails to validate object existence before performing operations on it. User interaction required (opening malicious PDF).

MitigationApply vendor patch/update to Foxit PhantomPDF; avoid opening untrusted PDF files from unknown sources.

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

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
    Check for Foxit Reader or PhantomPDF installation in Program Files (typically C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\) or via Windows Add/Remove Programs
    Affected if Either Foxit Reader or PhantomPDF is installed on the system
  2. Retrieve Foxit Reader version
    For Foxit Reader: right-click the executable (FoxitReader.exe), select Properties, then view the Details tab for the Product Version field. Alternatively, open Foxit Reader, go to Help > About Foxit Reader to display the version number
    Affected if Version number displayed is 10.1.0.37527 or lower
  3. Retrieve PhantomPDF version
    For PhantomPDF: right-click the executable (PhantomPDF.exe), select Properties, then view the Details tab for the Product Version field. Alternatively, open PhantomPDF, go to Help > About Foxit PhantomPDF to display the version number
    Affected if Version number displayed is 10.1.0.37527 or lower
  4. Confirm vulnerability applicability
    This vulnerability is triggered automatically when opening any PDF containing U3D (3D) objects. No specific feature configuration need be enabled - the flaw exists in the core U3D parsing logic
    Affected if The installed Foxit product version is <= 10.1.0.37527 and users open PDF files from untrusted sources

You are affected if Foxit Reader or PhantomPDF is installed with a version number at or below 10.1.0.37527.

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 10.1.0.37527
Interim mitigation

Apply vendor patch/update to Foxit PhantomPDF; avoid opening untrusted PDF files from unknown sources.

Fix this in Foxit Reader Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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