CVE-2019-6775
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 exportValues method within a AcroForm. 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-8491.
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 Reader 9.5.0.20723 contains a use-after-free or null-dereference vulnerability in the AcroForm exportValues method. The method fails to validate object existence before performing operations, allowing remote attackers to execute arbitrary code via malicious PDF files 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<= 9.5.0.20723<= 8.3.10.42705>= 9.0, <= 9.5.0.20723CVSS 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 if Foxit Reader is installedCheck for Foxit Reader in installed programs via Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\FoxitReader) or look for Foxit Reader in C:\Program Files\ or C:\Program Files (x86)\Affected if Foxit Reader is found on the system
-
Identify if Foxit PhantomPDF is installedCheck for PhantomPDF in installed programs via Windows Registry or look in C:\Program Files\ or C:\Program Files (x86)\ for PhantomPDF folderAffected if Foxit PhantomPDF is found on the system
-
Determine the installed Foxit Reader versionRight-click the Foxit Reader executable (FoxitReader.exe), select Properties, and check the Details tab for Product Version, or open Foxit Reader and go to Help > About Foxit ReaderAffected if The version is 9.5.0.20723 or any version lower than this (9.5.0.20723)
-
Determine the installed PhantomPDF versionRight-click the PhantomPDF executable (PhantomPDF.exe), select Properties, and check the Details tab for Product Version, or open PhantomPDF and go to Help > AboutAffected if The version is 8.3.10.42705 or lower, OR between 9.0 and 9.5.0.20723 inclusive
-
Assess exposure to untrusted PDFsConsider whether you or your users open PDF files from untrusted or unknown sources, as exploitation requires user interaction to open a malicious PDF fileAffected if Users routinely open PDF attachments or files from untrusted sources without verification
You are affected if Foxit Reader version 9.5.0.20723 or lower, or PhantomPDF version 8.3.10.42705 or lower, or PhantomPDF version 9.0 through 9.5.0.20723 is installed, and users open untrusted 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.
From vendor dataUpdate Foxit Reader to the latest patched version. Avoid opening untrusted PDF files from unknown sources.
- 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-2019-6775 — 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-6775 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