CVE-2022-28672
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-16640.
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 confidenceFoxit PDF Reader 11.2.1.53537 contains a use-after-free or null-dereference vulnerability in its Doc object handling. The application fails to validate the existence of an object before performing operations on it, allowing an attacker to execute arbitrary code in the context of the current process via a maliciously crafted PDF file or webpage.
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 in installed programs via Control Panel > Programs and Features, or check the default installation path at C:\Program Files\Foxit Software\Foxit PDF Reader\ or C:\Program Files (x86)\Foxit Software\Foxit PDF Reader\Affected if Foxit PDF Reader is installed and its version is <= 11.2.1.53537
-
Check if Foxit PDF Editor is installedLook for Foxit PDF Editor (formerly Foxit PhantomPDF) in installed programs, or check the default installation path at C:\Program Files\Foxit Software\Foxit PDF Editor\ or C:\Program Files (x86)\Foxit Software\Foxit PDF Editor\Affected if Foxit PDF Editor is installed and its version is <= 10.1.7.37777 or >= 11.0 and <= 11.2.1.53537
-
Determine the exact version number of Foxit PDF ReaderRight-click the Foxit PDF Reader executable (FoxitReader.exe) in the installation folder, select Properties, and view the Details tab for the Product Version field. Alternatively, open Foxit PDF Reader and go to Help > About Foxit PDF ReaderAffected if The displayed version is 11.2.1.53537 or any earlier version within the affected range
-
Determine the exact version number of Foxit PDF EditorRight-click the Foxit PDF Editor executable (FoxitPDFEditor.exe) in the installation folder, select Properties, and view the Details tab for the Product Version field. Alternatively, open Foxit PDF Editor and go to Help > About Foxit PDF EditorAffected if The displayed version is <= 10.1.7.37777 or >= 11.0 and <= 11.2.1.53537
-
Compare your installed version against affected rangesDocument the full version number (including build number) from the About dialog or file properties, then compare: For Reader, any version <= 11.2.1.53537 is affected. For Editor, versions <= 10.1.7.37777 or >= 11.0 through 11.2.1.53537 are affectedAffected if The installed version falls within any of the affected version ranges listed
You are affected if Foxit PDF Reader or Foxit PDF Editor is installed with a version number that matches or is lower than the affected ranges (Reader <= 11.2.1.53537, Editor <= 10.1.7.37777 or 11.0-11.2.1.53537).
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.
From vendor dataUpdate Foxit PDF Reader to the latest version containing the vendor patch. Avoid opening untrusted PDF files or visiting malicious webpages until the update is applied.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-28672 — 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-28672 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