CVE-2022-28669
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 · uneditedThis 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 Doc 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-16420.
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 confidenceThis is a use-after-free or null pointer dereference vulnerability in Foxit PDF Reader 11.2.1.53537 where the Doc object handling routine fails to validate object existence before performing operations on it. An attacker can exploit this by crafting a malicious PDF file that, when opened, allows arbitrary code execution in the context of the current process.
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<= 10.1.7.37777>= 11.0, <= 11.2.1.53537<= 11.2.1.53537CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Foxit PDF Reader is installedLook for Foxit PDF Reader executable in common installation paths: C:\Program Files\Foxit Software\Foxit Reader\FoxitReader.exe or C:\Program Files (x86)\Foxit Software\Foxit Reader\FoxitReader.exe. You can also check Add/Remove Programs for Foxit PDF Reader.Affected if Foxit PDF Reader is found on the system
-
Check if Foxit PDF Editor is installedLook for Foxit PDF Editor executable in common installation paths: C:\Program Files\Foxit Software\Foxit PDF Editor\FoxitPDFEditor.exe or C:\Program Files (x86)\Foxit Software\Foxit PDF Editor\FoxitPDFEditor.exe. You can also check Add/Remove Programs for Foxit PDF Editor.Affected if Foxit PDF Editor is found on the system
-
Obtain the installed version numberRight-click the Foxit executable (FoxitReader.exe or FoxitPDFEditor.exe), select Properties, and view the Details tab for the Product Version. Alternatively, open Foxit, go to Help > About to see the version.Affected if Unable to determine the version number (product may not be installed)
-
Compare against affected version rangesFor Foxit PDF Reader: any version up to and including 11.2.1.53537 is affected. For Foxit PDF Editor: any version <= 10.1.7.37777 OR versions 11.0 through 11.2.1.53537 are affected.Affected if Installed version falls within the affected ranges: Foxit PDF Reader <= 11.2.1.53537, or Foxit PDF Editor <= 10.1.7.37777, or Foxit PDF Editor >= 11.0 and <= 11.2.1.53537
A user is affected if Foxit PDF Reader version 11.2.1.53537 or earlier is installed, or if Foxit PDF Editor version 10.1.7.37777 or earlier, or any version 11.0 through 11.2.1.53537 is installed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply the vendor patch from Foxit; until then, avoid opening untrusted PDF files and disable JavaScript execution in the PDF reader as a defense-in-depth measure.
Foxit PDF Reader 11.2.2 or later / Foxit PDF Editor 11.2.2 or later (11.x branch) or 10.1.8 or later (10.x branch)
- Navigate to the official Foxit website (www.foxit.com) and locate the downloads section for Foxit PDF Reader
- Download the latest version of Foxit PDF Reader (version 11.2.2 or later)
- Download the latest version of Foxit PDF Editor (version 11.2.2 or later for the 11.x branch, or version 10.1.8 or later for the 10.x branch)
- Close any running instances of Foxit PDF Reader or PDF Editor
- Install the downloaded update by running the installer executable
- Restart the application after installation completes
- Verify the installed version matches the latest stable release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28669 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28669 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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