reader is a software product offered by foxitsoftware. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The significant number of reported vulnerabilities indicates this product has received substantial security scrutiny and community focus over time. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.
SecUtils has identified 259 known vulnerabilities affecting foxitsoftware reader. This includes 10 critical-severity issues and 229 high-severity issues that warrant immediate attention. Vulnerabilities in this product have been disclosed spanning from 2009 to 2021, indicating a sustained research interest and ongoing security attention. 14 medium-severity issues and 6 low-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2009-0836 | 2009-03-10 | 2025-04-09 | - | 10.0 | Likely |
| CVE-2016-8856 | 2016-10-31 | 2025-04-12 | 7.8 | 4.6 | Unknown |
| CVE-2016-8875 | 2016-10-31 | 2025-04-12 | 5.3 | 4.3 | Likely |
| CVE-2016-8876 | 2016-10-31 | 2025-04-12 | 7.5 | 6.8 | Likely |
| CVE-2016-8877 | 2016-10-31 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-8878 | 2016-10-31 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-8879 | 2016-10-31 | 2025-04-12 | 6.5 | 4.3 | Likely |
| CVE-2016-8334 | 2017-01-06 | 2025-04-20 | 6.8 | 4.3 | Likely |
| CVE-2018-5674 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5675 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5676 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5677 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5678 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5679 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-5680 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-7406 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-7407 | 2018-05-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17607 | 2018-09-28 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-17608 | 2018-09-28 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-17609 | 2018-09-28 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-17610 | 2018-09-28 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-17611 | 2018-09-28 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2018-17781 | 2018-09-29 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-3943 | 2018-10-02 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3944 | 2018-10-02 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3957 | 2018-10-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3958 | 2018-10-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3959 | 2018-10-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3960 | 2018-10-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3961 | 2018-10-02 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3962 | 2018-10-02 | 2024-11-21 | 7.3 | 6.0 | Unknown |
| CVE-2018-3946 | 2018-10-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3964 | 2018-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3965 | 2018-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3966 | 2018-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3967 | 2018-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3993 | 2018-10-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3994 | 2018-10-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3995 | 2018-10-03 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-16291 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16292 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16293 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16294 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16295 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16296 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-16297 | 2018-10-08 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2018-3940 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3941 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3942 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3945 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3992 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3996 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3997 | 2018-10-08 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17615 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17616 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17617 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17618 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17619 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17620 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17621 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17622 | 2018-10-29 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2018-17623 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17624 | 2018-10-29 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17625 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17626 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17627 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17628 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17629 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17630 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17631 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17632 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17633 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17634 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17635 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17636 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17637 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17638 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17639 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17640 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17641 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17642 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17643 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17644 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17645 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17646 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17647 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17648 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17649 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17650 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17651 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17652 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17653 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17654 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17655 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17656 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17657 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17658 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17659 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17660 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17661 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17662 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17663 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17664 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17665 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17666 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17667 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17668 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17669 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17670 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17671 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17672 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17673 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17674 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17675 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17676 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17677 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17678 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17679 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17680 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17681 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17682 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17683 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17684 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17685 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17686 | 2019-01-24 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2018-17687 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17688 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17689 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17690 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17691 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17692 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17693 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17694 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17695 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17696 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17697 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17698 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17699 | 2019-01-24 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2018-17700 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17701 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17702 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17703 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17704 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-17705 | 2019-01-24 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-3956 | 2019-01-30 | 2024-11-21 | 7.1 | 5.8 | Likely |
| CVE-2019-6727 | 2019-03-21 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-6728 | 2019-03-21 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-6729 | 2019-03-21 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-6730 | 2019-03-21 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-6731 | 2019-03-21 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-6732 | 2019-03-21 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-6733 | 2019-03-21 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-6734 | 2019-03-21 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-6735 | 2019-03-21 | 2024-11-21 | 6.5 | 4.3 | Likely |
| CVE-2019-5031 | 2019-10-02 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-13326 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13327 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13328 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13329 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13330 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13331 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13332 | 2019-10-03 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13315 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13316 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13317 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13318 | 2019-10-04 | 2024-11-21 | 5.5 | 4.3 | Likely |
| CVE-2019-13319 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-13320 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-6774 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-6775 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-6776 | 2019-10-04 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2019-17183 | 2019-10-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-5126 | 2020-01-16 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-5130 | 2020-01-16 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-5131 | 2020-01-16 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2019-5145 | 2020-01-16 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2020-8844 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8845 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8846 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8847 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8848 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8849 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8850 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8851 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8852 | 2020-02-14 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-8853 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8854 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8855 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8856 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-8857 | 2020-02-14 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10889 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10890 | 2020-04-22 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2020-10891 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10892 | 2020-04-22 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2020-10893 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10894 | 2020-04-22 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-10895 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10896 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10897 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10898 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10899 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10900 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10901 | 2020-04-22 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-10902 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10903 | 2020-04-22 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-10904 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10905 | 2020-04-22 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-10906 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10907 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10908 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10909 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10910 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10911 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-10912 | 2020-04-22 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-13803 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13804 | 2020-06-04 | 2024-11-21 | 9.8 | 6.8 | Likely |
| CVE-2020-13805 | 2020-06-04 | 2024-11-21 | 9.8 | 5.0 | Likely |
| CVE-2020-13806 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13807 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13808 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13809 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13810 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20817 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20818 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20819 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20820 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-13814 | 2020-06-04 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2020-13815 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-21236 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2018-21239 | 2020-06-04 | 2024-11-21 | 5.3 | 5.0 | Likely |
| CVE-2018-21240 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20826 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20827 | 2020-06-04 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2019-20828 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20829 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20830 | 2020-06-04 | 2024-11-21 | 9.8 | 7.5 | Likely |
| CVE-2019-20835 | 2020-06-04 | 2024-11-21 | 4.3 | 4.3 | Likely |
| CVE-2019-20836 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2019-20837 | 2020-06-04 | 2024-11-21 | 7.5 | 5.0 | Likely |
| CVE-2020-15637 | 2020-08-20 | 2024-11-21 | 3.3 | 4.3 | Likely |
| CVE-2020-15638 | 2020-08-20 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2020-11493 | 2020-09-04 | 2024-11-21 | 8.1 | 5.8 | Likely |
| CVE-2020-12247 | 2020-09-04 | 2024-11-21 | 7.1 | 5.8 | Likely |
| CVE-2020-12248 | 2020-09-04 | 2024-11-21 | 8.8 | 6.8 | Likely |
| CVE-2018-20309 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20310 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20311 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20312 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20313 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20314 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20315 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2018-20316 | 2021-01-07 | 2024-11-21 | 8.1 | 6.8 | Likely |
| CVE-2021-31456 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31457 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31458 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31459 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31460 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31461 | 2021-05-07 | 2024-11-21 | 7.8 | 6.8 | Likely |
| CVE-2021-31473 | 2021-05-21 | 2024-11-21 | 7.8 | 6.8 | Likely |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records for foxitsoftware reader by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.