How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "xpdf"

Found 5 matching products. Filters apply to all results.

You can search for specific versions with /product/xpdf/1.2.3

xpdf / xpdf

26 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2009-4035	High	December 21, 2009 12/21/09	== 3.0.0
CVE-2007-4352	High	November 8, 2007 11/8/07	== 3.0.1_pl1
CVE-2007-5392	High	November 8, 2007 11/8/07	== 3.0.1_pl1
CVE-2007-5393	High	November 8, 2007 11/8/07	== 3.02p11
CVE-2007-0104	Medium	January 9, 2007 1/9/07	== 3.0.1_pl1 == 3.0.1 == 3.0.1_pl2 == 3.0_pl2 == 3.0
CVE-2006-1244	High	March 15, 2006 3/15/06	== 2.0 == 3.0_pl3 == 1.0 == 3.0.1_pl1 == 0.91 == 2.3 == 0.92 == 3.0.1 == 1.0a == 2.2 == 3.0_pl2 == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2006-0746	High	March 9, 2006 3/9/06	*
CVE-2006-0301	High	January 30, 2006 1/30/06	*
CVE-2005-3624	Medium	December 31, 2005 12/31/05	== 3.0
CVE-2005-3625	High	December 31, 2005 12/31/05	== 3.0
CVE-2005-3626	Medium	December 31, 2005 12/31/05	== 3.0
CVE-2005-3627	High	December 31, 2005 12/31/05	*
CVE-2005-3628	High	December 31, 2005 12/31/05	*
CVE-2005-3192	High	December 8, 2005 12/8/05	== 3.0.1
CVE-2005-3191	Medium	December 7, 2005 12/7/05	== 2.0 == 3.0_pl3 == 1.0 == 0.91 == 2.3 == 0.92 == 3.0.1 == 1.0a == 2.2 == 3.0_pl2 == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2005-3193	Medium	December 7, 2005 12/7/05	== 2.0 == 3.0_pl3 == 1.0 == 0.91 == 2.3 == 0.92 == 3.0.1 == 1.0a == 2.2 == 3.0_pl2 == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2005-2097	Low	August 16, 2005 8/16/05	== 3.0_pl3 == 3.0_pl2 == 3.0
CVE-2005-0064	High	May 2, 2005 5/2/05	== 2.0 == 0.91a == 0.6 == 1.0 == 0.93a == 0.5 == 0.80 == 0.91 == 0.93c == 0.92a == 0.2 == 2.3 == 0.92 == 0.93b == 1.0a == 0.5a == 0.92c == 0.3 == 0.7a == 0.92d == 2.2 == 0.92b == 2.1 == 0.90 == 3.0 == 0.92e == 0.91c == 0.93 == 0.91b == 0.4 == 0.7 == 1.1
CVE-2005-0206	High	April 27, 2005 4/27/05	== 2.0 == 1.0 == 0.91 == 2.3 == 0.92 == 1.0a == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2004-0888	High	January 27, 2005 1/27/05	== 2.0 == 1.0 == 0.91 == 2.3 == 0.92 == 1.0a == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2004-0889	High	January 27, 2005 1/27/05	== 2.0 == 1.0 == 0.91 == 2.3 == 0.92 == 1.0a == 2.1 == 0.90 == 3.0 == 0.93 == 1.1
CVE-2004-1125	High	January 10, 2005 1/10/05	== 3.0
CVE-2003-0434	High	July 24, 2003 7/24/03	== 1.1
CVE-2002-1384	High	January 2, 2003 1/2/03	== 2.0 == 1.0 == 0.91 == 1.0a == 2.1 == 0.90 == 1.1
CVE-2000-0727	High	October 20, 2000 10/20/00	== 0.90
CVE-2000-0728	High	October 20, 2000 10/20/00	== 0.90

xpdfreader / xpdf

82 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-7868	High	August 15, 2024 8/15/24	< 4.06
CVE-2024-7866	Medium	August 15, 2024 8/15/24	<= 4.05
CVE-2024-7867	Medium	August 15, 2024 8/15/24	<= 4.05
CVE-2024-4976	Medium	May 15, 2024 5/15/24	<= 4.05
CVE-2024-4568	Low	May 6, 2024 5/6/24	<= 4.05
CVE-2024-4141	Low	April 24, 2024 4/24/24	<= 4.05
CVE-2024-3900	Low	April 17, 2024 4/17/24	<= 4.05
CVE-2024-3247	Low	April 2, 2024 4/2/24	<= 4.05
CVE-2024-3248	Low	April 2, 2024 4/2/24	<= 4.05
CVE-2024-2971	Low	March 26, 2024 3/26/24	<= 4.05
CVE-2022-48545	Medium	August 22, 2023 8/22/23	== 4.02
CVE-2023-3436	Low	June 27, 2023 6/27/23	== 4.04
CVE-2023-3044	Low	June 2, 2023 6/2/23	< 4.05
CVE-2023-2664	Low	May 11, 2023 5/11/23	<= 4.04
CVE-2023-2663	Low	May 11, 2023 5/11/23	<= 4.04
CVE-2023-2662	Low	May 11, 2023 5/11/23	<= 4.04
CVE-2023-26930	Medium	April 26, 2023 4/26/23	== 4.04
CVE-2022-45586	Medium	February 15, 2023 2/15/23	== 4.04
CVE-2022-45587	Medium	February 15, 2023 2/15/23	== 4.04
CVE-2021-36493	High	February 3, 2023 2/3/23	== 4.03
CVE-2022-43071	Medium	November 15, 2022 11/15/22	== 4.04
CVE-2022-43295	Medium	November 14, 2022 11/14/22	== 4.04
CVE-2022-41842	Medium	September 30, 2022 9/30/22	== 4.04
CVE-2022-41843	Medium	September 30, 2022 9/30/22	== 4.04
CVE-2022-41844	Medium	September 30, 2022 9/30/22	== 4.04
CVE-2022-38222	High	September 29, 2022 9/29/22	== 4.04
CVE-2022-38928	High	September 21, 2022 9/21/22	== 4.04
CVE-2022-38334	Medium	September 15, 2022 9/15/22	<= 4.04
CVE-2022-36561	Medium	August 30, 2022 8/30/22	== 4.04
CVE-2022-38171	High	August 22, 2022 8/22/22	== 4.04
CVE-2022-33108	High	June 28, 2022 6/28/22	== 4.04
CVE-2021-27548	Medium	May 18, 2022 5/18/22	== 4.03
CVE-2022-30775	Medium	May 16, 2022 5/16/22	== 4.04
CVE-2022-30524	High	May 9, 2022 5/9/22	== 4.0.4
CVE-2022-27135	Medium	April 25, 2022 4/25/22	== 4.03
CVE-2021-30860	High	August 24, 2021 8/24/21	< 4.04
CVE-2020-35376	High	December 26, 2020 12/26/20	== 4.02
CVE-2020-25725	Medium	November 21, 2020 11/21/20	== 4.02
CVE-2020-24996	High	September 3, 2020 9/3/20	== 4.0.2
CVE-2020-24999	High	September 3, 2020 9/3/20	== 4.0.2
CVE-2012-2142	High	January 9, 2020 1/9/20	== 3.02
CVE-2010-0206	Medium	October 30, 2019 10/30/19	== 3.03-17 == 3.04-4 == 3.04-13
CVE-2010-0207	Medium	October 30, 2019 10/30/19	== 3.03-17 == 3.04-4 == 3.04-13
CVE-2019-10018	Medium	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10019	Low	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10020	Low	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10021	Low	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10022	Low	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10023	Low	March 25, 2019 3/25/19	== 4.01.01
CVE-2019-10024	Low	March 25, 2019 3/25/19	== 4.01.01

foolabs / xpdf

23 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-1552	Low	March 31, 2011 3/31/11	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1 == 3.02pl1 == 3.02pl2 == 3.02pl3 == 3.02pl4
CVE-2011-1553	Low	March 31, 2011 3/31/11	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1 == 3.02pl1 == 3.02pl2 == 3.02pl3 == 3.02pl4
CVE-2011-1554	Low	March 31, 2011 3/31/11	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1 == 3.02pl1 == 3.02pl2 == 3.02pl3 == 3.02pl4
CVE-2011-0764	Medium	March 31, 2011 3/31/11	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1 == 3.02pl1 == 3.02pl2 == 3.02pl3 == 3.02pl4
CVE-2010-3704	Medium	November 5, 2010 11/5/10	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1 == 3.02pl1 == 3.02pl2 == 3.02pl3
CVE-2009-3603	High	October 21, 2009 10/21/09	== 3.02pl3 == 3.02pl1 == 3.02pl2
CVE-2009-3604	High	October 21, 2009 10/21/09	== 3.02pl1 == 3.02pl2 == 3.02pl3
CVE-2009-3606	High	October 21, 2009 10/21/09	== 3.02pl1 == 3.02pl2 == 3.02pl3
CVE-2009-3608	High	October 21, 2009 10/21/09	== 3.02pl1 == 3.02pl2 == 3.02pl3
CVE-2009-3609	Low	October 21, 2009 10/21/09	== 3.02pl1 == 3.02pl2 == 3.02pl3
CVE-2009-0165	High	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1
CVE-2009-0146	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-0147	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-0166	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-0195	Medium	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a == 3.0.1
CVE-2009-0799	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-0800	Medium	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1179	Medium	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1180	Medium	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1181	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1182	High	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1183	Low	April 23, 2009 4/23/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a
CVE-2009-1144	Medium	April 9, 2009 4/9/09	== 0.5a == 0.7a == 0.91a == 0.91b == 0.91c == 0.92a == 0.92b == 0.92c == 0.92d == 0.92e == 0.93a == 0.93b == 0.93c == 1.00a

glyphandcog / xpdf

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2019-16927	Medium		September 27, 2019 9/27/19	== 4.01.01
CVE-2011-2902	Medium		January 30, 2018 1/30/18	< 3.02-19

xpdf_project / xpdf

11 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-38235	Medium	August 16, 2022 8/16/22	== 3.04
CVE-2022-38236	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38237	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38238	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38227	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38228	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38229	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38230	Medium	August 16, 2022 8/16/22	== 3.04
CVE-2022-38231	High	August 16, 2022 8/16/22	== 3.04
CVE-2022-38233	Medium	August 16, 2022 8/16/22	== 3.04
CVE-2022-38234	Medium	August 16, 2022 8/16/22	== 3.04

Showing vulnerabilities for 5 products matching "xpdf". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.