CVE-2019-13326
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 Reader 9.5.0.20723. 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 processing of fields within Acroform 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-8864.
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 Reader's Acroform field processing. The lack of validating object existence prior to operations allows remote attackers to execute arbitrary code via malicious PDF files. User interaction is required (opening a malicious PDF).
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<= 9.6.0.25114CVSS 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 Reader versionOpen Foxit Reader, go to Help > About Foxit Reader, or right-click the Foxit Reader executable file and select Properties > Details to view the Product VersionAffected if The displayed version number is 9.6.0.25114 or earlier
-
Compare version against affected rangeIf version is shown as a 4-part number (such as 9.6.0.25114), compare each segment: affected if the first segment is less than 9, OR if first segment equals 9 and second segment is less than 6, OR if first segment equals 9 and second segment equals 6 and third segment equals 0 and fourth segment is less than or equal to 25114Affected if Version falls at or below 9.6.0.25114
-
Confirm Acroform functionality is in useOpen a PDF document in Foxit Reader and check if the document contains fillable form fields (AcroForms). Look for form fields in the document or use the Form tool under the Home or Edit tab to detect formsAffected if PDFs with Acroform fields are being opened or edited in Foxit Reader
-
Verify JavaScript execution stateIn Foxit Reader, go to File > Preferences > JavaScript and check if JavaScript is enabledAffected if JavaScript execution is enabled (this increases exploitability but the vulnerability can still trigger via Acroform processing alone)
A user is affected if Foxit Reader version is 9.6.0.25114 or earlier and the application is used to open PDF documents, particularly those containing Acroform fields.
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 dataUpgrade Foxit Reader to the latest patched version. Until patched, avoid opening untrusted PDF files and consider disabling JavaScript execution in Foxit Reader settings.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13326 — 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-2019-13326 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