CVE-2022-28683
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 deletePages method. 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-16828.
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 or null pointer dereference vulnerability exists in Foxit PDF Reader 11.2.1.53537 within the deletePages method. The application fails to validate object existence before performing operations on it, allowing remote attackers to execute arbitrary code via malicious PDF files that trigger the deletePages function.
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.
-
Identify installed Foxit productCheck for Foxit PDF Reader or Foxit PDF Editor installation. On Windows, look in Program Files for Foxit PDF Reader or Foxit PDF Editor folders, or check Add/Remove Programs. The executable is typically named FoxitPDFReader.exe or FoxitPDFEditor.exeAffected if Either Foxit PDF Reader or Foxit PDF Editor is installed
-
Determine installed version numberRight-click the FoxitPDFReader.exe or FoxitPDFEditor.exe file in the installation directory, select Properties, and view the Details tab for the Product Version field. Alternatively, open the application and go to Help > About Foxit PDF Reader/EditorAffected if Version cannot be determined or is within affected ranges
-
Compare Reader version to affected rangeIf Foxit PDF Reader is installed, compare the installed version to affected range: any version <= 11.2.1.53537Affected if Foxit PDF Reader version is 11.2.1.53537 or earlier
-
Compare Editor version to affected rangesIf Foxit PDF Editor is installed, compare the installed version to affected ranges: any version <= 10.1.7.37777 OR any version from 11.0.0.0 through 11.2.1.53537Affected if Foxit PDF Editor version is 10.1.7.37777 or earlier, or between 11.0.0.0 and 11.2.1.53537 inclusive
The environment is affected if Foxit PDF Reader version <= 11.2.1.53537 or Foxit PDF Editor version <= 10.1.7.37777 or between 11.0 and 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 · scopedUpdate Foxit PDF Reader to the vendor-patched version. Until patched, avoid opening PDF files from untrusted sources.
Latest version of Foxit PDF Reader/PDF Editor (version greater than 11.2.1.53537)
- 1. Navigate to the official Foxit software download page at www.foxit.com
- 2. Locate and download the latest version of Foxit PDF Reader or PDF Editor
- 3. Uninstall the current version of Foxit PDF Reader (version 11.2.1.53537 or earlier) or PDF Editor
- 4. Install the latest downloaded version of the Foxit software
- 5. Verify the installation was successful by checking the software version in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28683 — 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-28683 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