dbcve.org
Pdf EditorApplication · Foxit

CVE-2022-28670

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 disclose sensitive information 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 processing of AcroForms. Crafted data in an AcroForm can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-16523.

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

Out-of-bounds read vulnerability in Foxit PDF Reader 11.2.1.53537 when processing crafted AcroForm data. The vulnerability allows remote attackers to read past the end of an allocated buffer, potentially disclosing sensitive information. While user interaction is required (opening a malicious PDF), the flaw can be chained with other vulnerabilities to achieve arbitrary code execution in the current process context.

MitigationUpdate Foxit PDF Reader to the latest version and avoid opening untrusted PDF files or visiting malicious pages. Disable JavaScript execution in the PDF reader as an additional hardening measure.

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
    Check for Foxit PDF Reader or Foxit PDF Editor in installed programs. On Windows, check 'Programs and Features' or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\
    Affected if Either Foxit PDF Reader or Foxit PDF Editor is present on the system
  2. Determine installed version number
    Open Foxit, go to Help > About Foxit PDF Reader/Editor, or check the executable properties of foxitreader.exe or foxitpdfeditor.exe in the installation directory
    Affected if The displayed version falls within the affected ranges: <= 10.1.7.37777 OR (>= 11.0 AND <= 11.2.1.53537)
  3. Verify AcroForm feature is accessible
    Attempt to open a PDF with AcroForm fields or check if AcroForm support is loaded. In Foxit, go to File > Properties > Forms to see if any forms are present, or verify the 'AcroForm' plugin is loaded in the Foxit plugins directory
    Affected if AcroForm functionality is available and the user can open PDF files containing AcroForm data
  4. Check JavaScript execution status
    In Foxit, go to Edit > Preferences > JavaScript. Also check File > Properties > Security for script permissions
    Affected if JavaScript execution is enabled, which increases the severity if a malicious PDF is opened

A user is affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version matching <= 10.1.7.37777 or >= 11.0 through 11.2.1.53537, and AcroForm processing is accessible when opening untrusted PDFs.

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

Update Foxit PDF Reader to the latest version and avoid opening untrusted PDF files or visiting malicious pages. Disable JavaScript execution in the PDF reader as an additional hardening measure.

Recommended fix Moderate confidence

Foxit PDF Reader 11.2.2 or later; Foxit PDF Editor 11.2.2 or later (for 11.x branch) and Foxit PDF Editor 10.1.8 or later (for 10.x branch)

  1. Download the latest version of Foxit PDF Reader or PDF Editor from the official Foxit website (www.foxit.com)
  2. Uninstall the current version of Foxit PDF Reader or PDF Editor
  3. Install the updated version that contains the security fix for CVE-2022-28670
Caveat Standard upgrade - review release notes for any feature changes in the new version

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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