CVE-2023-51556
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 · uneditedFoxit PDF Reader AcroForm Doc Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Foxit PDF Reader. 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-22255.
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 contains a use-after-free vulnerability in AcroForm Doc object handling. The software fails to validate object existence before performing operations, allowing a remote attacker to execute arbitrary code via a maliciously crafted PDF file requiring user interaction.
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.12.37872>= 11.0.0, <= 11.2.7.53812>= 12.0.0, <= 12.1.3.15356= 13.0.0.21632= 2023.1.0.15510= 2023.2.0.21408<= 2023.2.0.21408CVSS 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.0/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 or Editor is installedOpen Control Panel > Programs and Features, or check common install paths such as C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\Affected if Foxit PDF Reader or Foxit PDF Editor is present on the system
-
Identify the installed Foxit versionIn Foxit, go to Help > About Foxit PDF Reader (or About Foxit PDF Editor). Alternatively, right-click the application in Programs and Features and select Properties to view the version, or check the executable file properties of foxitreader.exe or foxitpdfeditor.exeAffected if A version number is displayed that can be compared to the affected ranges
-
Compare the installed version against affected rangesCompare your installed version to these affected ranges: Foxit Pdf Editor <= 10.1.12.37872; >= 11.0.0 through <= 11.2.7.53812; >= 12.0.0 through <= 12.1.3.15356; = 13.0.0.21632; = 2023.1.0.15510; = 2023.2.0.21408. For Foxit Pdf Reader, any version <= 2023.2.0.21408 is affectedAffected if The installed version matches or falls within any of the listed affected version ranges
-
Confirm the vulnerability trigger conditionThe vulnerability exploits AcroForm Doc object handling in PDF files. Verify if the user frequently opens PDF files from untrusted sources, as exploitation requires a user to open a maliciously crafted PDF fileAffected if Users open PDF files, particularly from untrusted or unknown sources, and the installed Foxit version is in the affected ranges
A user is affected if Foxit PDF Reader version <= 2023.2.0.21408 or Foxit PDF Editor version matching any of the specified vulnerable ranges is installed and users open PDF files.
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 latest patched version. Avoid opening untrusted PDF files and disable JavaScript execution in PDF readers as additional defense-in-depth measures.
Latest available Foxit PDF Reader/PDF Editor version (contact Foxit support or visit foxit.com for exact version numbers post-fix)
- 1. Open Foxit PDF Reader or PDF Editor application
- 2. Click on 'Help' in the menu bar
- 3. Select 'Check for Updates' or navigate to the official Foxit website at www.foxit.com to download the latest version
- 4. Download and install the latest version of Foxit PDF Reader or PDF Editor
- 5. Restart the application if prompted
- 6. Verify the installed version matches or exceeds the latest available release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-51556 — 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-2023-51556 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