Security readout for executives and security teams
Plain-English summary
Foxit PhantomPDF before 8.3.10 has a documented JavaScript denial-of-service issue. The known business impact is disruption of the PDF application, not confirmed data theft or code execution. Public sources do not provide CVSS scoring or evidence of active exploitation.
Executive priority
Treat as a low-priority availability risk unless legacy Foxit PhantomPDF is broadly deployed or used in high-volume document workflows.
Technical view
The CVE describes a JavaScript DoS in Foxit PhantomPDF before 8.3.10. A one-page document can trigger the issue when pages are deleted through a t.hidden = true call. Public metadata lacks CVSS, CWE, root-cause detail, and platform-specific build information.
Likely exposure
Exposure is most likely on endpoints still running Foxit PhantomPDF versions earlier than 8.3.10, especially where users open untrusted PDFs.
Exploitation context
The source bundle does not cite KEV listing or active exploitation. The described condition requires a crafted document interaction path and results in denial of service.
Researcher notes
Evidence is sparse: no CVSS, CWE, exploit status, or detailed vendor advisory text is included. Analysis should stay limited to PhantomPDF before 8.3.10 and JavaScript-triggered denial of service.
Mitigation direction
- Identify Foxit PhantomPDF installations and versions across managed endpoints.
- Upgrade versions earlier than 8.3.10 according to Foxit vendor guidance.
- Restrict untrusted PDF handling on unsupported or unpatched systems.
- Check Foxit security bulletins for current remediation details.
Validation and detection
- Confirm endpoint inventory includes Foxit PhantomPDF version data.
- Verify no managed systems run PhantomPDF earlier than 8.3.10.
- Review email, web, and EDR telemetry for suspicious PDF delivery patterns.
- Document exceptions where legacy Foxit versions remain in use.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2019-14214 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.foxitsoftware.com/support/security-bulletins.phpCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.