An issue was discovered in Foxit PhantomPDF before 8.3.11.

published 2019-07-21 7y ago modified 2026-06-17 4mo ago also EUVD-2019-5461

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.7%; EPSS 1.7% chance of exploitation in 30 days, percentile 76%
public exploits: 0; none known

An issue was discovered in Foxit PhantomPDF before 8.3.11. The application could crash due to the lack of proper validation of the existence of an object prior to performing operations on that object when executing JavaScript.

Patch / fix

fixed in 1

foxitsoftware phantompdf 8.3.11

Is CVE-2019-14211 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.66% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-20 Improper Input Validation

References

foxitsoftware.com /support/security-bulletins.php
vendor-advisory
securityfocus.com /bid/109358
vdb-entry, broken-link

Sources

CVE List CVE-2019-14211
NVD CVE-2019-14211

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.