CVE-2022-28680
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 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-16821.
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 confidenceA use-after-free vulnerability in Foxit PDF Reader 11.2.1.53537 allows remote attackers to execute arbitrary code via a malicious PDF file. The flaw exists in the Annotation object handling where the code fails to validate object existence before performing operations on it, leading to memory corruption that can be leveraged for code execution in the current process context.
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.37777CVSS 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 software is installedOn Windows, check Registry key HKLM\SOFTWARE\Foxit Software or look for Foxit Reader or Foxit PDF Editor in Programs and Features. On Mac, check /Applications folder for Foxit apps.Affected if No Foxit PDF software is found, the system is not affected by this specific vulnerability.
-
Identify the exact Foxit version numberIn Foxit PDF Reader/Editor, go to Help > About Foxit PDF Reader (or similar menu item) to display the exact version number. Alternatively, right-click the desktop shortcut, select Properties, and check the version in the Details tab.Affected if The version cannot be determined, but the system may still be vulnerable if Foxit is present.
-
Compare installed version against affected rangeCompare your installed version to the affected version <= 10.1.7.37777 as listed in the affected products. If your version is 10.1.7.37777 or lower, the version is within the affected range.Affected if Installed version is 10.1.7.37777 or lower (any version at or below this threshold).
If Foxit PDF Reader or Editor is installed and the version is 10.1.7.37777 or lower, the environment is within the affected version range for this CVE.
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 · scopedUpdate Foxit PDF Reader to the vendor-patched version. Avoid opening untrusted PDF files from unknown sources.
Latest Foxit PDF Reader version (post 11.2.1.53537)
- 1. Open Foxit PDF Reader application
- 2. Navigate to Help > Check for Updates or About Foxit PDF Reader
- 3. Download and install the latest available version from the official Foxit website at www.foxit.com
- 4. Alternatively, visit www.foxit.com and navigate to the Downloads section for PDF Reader
- 5. Install the newest version available to address the Use After Free vulnerability (CVE-2022-28680)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28680 — 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-28680 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