Pdf EditorApplication · Foxit

CVE-2022-28677

HIGH · 7.8 CVSS v3.1 Published 2022-07-18
Fix available
A fix is available. Upgrade to after 11.2.1.53537 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 PDF Reader 11.2.1.53537. 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 Annotation objects. 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-16663.

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

This is a use-after-free or null pointer dereference vulnerability in Foxit PDF Reader 11.2.1.53537. The flaw exists in the handling of Annotation objects where the code fails to validate that an object exists before performing operations on it. An attacker can exploit this by tricking a user into opening a malicious PDF file, allowing arbitrary code execution in the context of the current process.

MitigationUpdate Foxit PDF Reader to the latest version and avoid opening PDF files from untrusted 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
Pdf EditorApplication
Affected:<= 10.1.7.37777>= 11.0, <= 11.2.1.53537
Pdf ReaderApplication
Affected:<= 11.2.1.53537

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. Verify Foxit PDF software is installed
    Check system for Foxit PDF Reader or Foxit PDF Editor applications. On Windows, review installed programs in Control Panel or use system inventory tools. On macOS, check the Applications folder.
    Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
  2. Determine installed Foxit version
    Open the Foxit application, then access Help > About Foxit [Reader/Editor] to display the exact version number and build information.
    Affected if The displayed version falls within an affected range: Foxit PDF Editor versions <= 10.1.7.37777 OR >= 11.0 through <= 11.2.1.53537; Foxit PDF Reader versions <= 11.2.1.53537
  3. Compare version against affected ranges
    If version is Foxit PDF Editor 10.x, check if it is 10.1.7.37777 or lower. If version is 11.x, check if it is 11.2.1.53537 or lower. Any version at or below these thresholds is affected.
    Affected if Installed version is 10.1.7.37777 or lower, OR is 11.0 through 11.2.1.53537 inclusive
  4. Confirm exposure to trigger condition
    The vulnerability is triggered when a user opens a maliciously crafted PDF file containing specially formatted Annotation objects. Review PDF files opened from untrusted sources.
    Affected if The user opens PDF files from untrusted or unknown sources using a vulnerable Foxit version

A system is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version <= 10.1.7.37777, or any version from 11.0 through 11.2.1.53537, and the user may open PDF files from untrusted sources.

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

Update Foxit PDF Reader to the latest version and avoid opening PDF files from untrusted sources.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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