dbcve.org
Pdf EditorApplication · Foxit

CVE-2022-28675

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-16642.

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's handling of Annotation objects. The code fails to validate that an object exists before performing operations on it, allowing a remote attacker to execute arbitrary code in the context of the current process via a maliciously crafted PDF file that requires user interaction to open.

MitigationApply the vendor-provided security patch by updating Foxit PDF Reader to the latest version. Until patched, avoid opening PDF files from untrusted sources and disable JavaScript execution in the reader if possible.

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. Identify installed Foxit product
    Open Windows Settings > Apps & Features or use Control Panel > Programs and Features to locate Foxit PDF Reader or Foxit PDF Editor in the installed programs list
    Affected if Either Foxit PDF Reader or Foxit PDF Editor is installed on the system
  2. Determine exact version number
    Launch Foxit PDF Reader/Editor, click Help > About or use the keyboard shortcut Ctrl+F8 to open the About dialog which displays the exact version and build number (for example: 11.2.1.53537)
    Affected if The displayed version matches one of the affected ranges: any version <= 10.1.7.37777, or any version from 11.0.0 through 11.2.1.53537 inclusive
  3. Check Windows registry for version
    Open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Foxit Software\Foxit Reader (or Editor) or HKEY_CURRENT_USER\SOFTWARE\Foxit Software\Foxit Reader, then locate the Version value in the right pane
    Affected if The registry Version value falls within the affected ranges: <= 10.1.7.37777, >= 11.0.0 and <= 11.2.1.53537

A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version number matching the vulnerable ranges: any build <= 10.1.7.37777, or any version from 11.0.0 through 11.2.1.53537 inclusive.

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
Upgrade available Upgrade to a release after 11.2.1.53537
Interim mitigation

Apply the vendor-provided security patch by updating Foxit PDF Reader to the latest version. Until patched, avoid opening PDF files from untrusted sources and disable JavaScript execution in the reader if possible.

Recommended fix Moderate confidence

Foxit PDF Reader/PDF Editor version 11.2.2 or later (verify via Help > Check for Updates)

  1. 1. Open Foxit PDF Reader or PDF Editor application
  2. 2. Navigate to Help > Check for Updates or About to identify current version
  3. 3. Download the latest version from the official Foxit website (www.foxit.com)
  4. 4. Uninstall the current version or run the installer to upgrade
  5. 5. Restart the application after upgrade completes

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

Fix this in Pdf Editor 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-2022-28675 — 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-2022-28675 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