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.

363,607

Total vulnerabilities in the database

Vulnerabilities for products matching "php_fusion"

Found 2 matching products. Filters apply to all results.

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

php_fusion / php_fusion

139 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2006-4673	Low	September 11, 2006 9/11/06	== 6.0.105 == 6.0.303 == 6.0.106 == 6.0.204 == 6.0.110 == 6.0.109 == 6.0.307 == 6.0.304 <= 6.01.4 == 6.0.107 == 6.0.206 == 6.0.306
CVE-2006-3555	Medium	July 13, 2006 7/13/06	== 6.00.307 == 6.0.105 == 6.00.105 == 6.00.106 == 6.00.103 == 6.00.101 == 6.0.106 == 6.00.107 == 6.00.303 == 6.00.3 == 6.00.104 == 6.01.2 == 6.00.100 == 6.00.108 == 6.00.207 == 6.00.306 == 6.00.304 == 6.00.200 == 6.00.110 == 6.0.107 == 6.00.102 == 6.00.205 == 6.00.109 == 6.00.206 == 6.00.204 == 6.00.300
CVE-2006-2459	Medium	May 19, 2006 5/19/06	== 6.00.307 == 6.00.306
CVE-2006-2330	Medium	May 12, 2006 5/12/06	== 6.00.105 == 6.00.106 == 6.00.107 == 6.00.303 == 6.00.3 == 6.00.306 == 6.00.304 == 6.00.110 == 6.00.109 == 6.00.206 == 6.00.204
CVE-2006-2331	Medium	May 12, 2006 5/12/06	== 6.00.105 == 6.00.106 == 6.00.107 == 6.00.303 == 6.00.3 == 6.00.306 == 6.00.304 == 6.00.110 == 6.00.109 == 6.00.206 == 6.00.204
CVE-2006-0593	Low	February 8, 2006 2/8/06	== 6.00.105 == 6.00.106 == 6.00.103 == 6.00.101 == 6.00.107 == 6.00.303 == 6.00.104 == 6.00.100 == 6.00.108 == 6.00.207 == 6.00.200 == 6.00.110 == 6.00.102 == 6.00.205 == 6.00.109 == 6.00.206 == 6.00.204 == 6.00.300
CVE-2005-4655	Low	December 31, 2005 12/31/05	== 6.00.204
CVE-2005-4516	Low	December 28, 2005 12/28/05	== 6.00.207 == 6.00.200 == 6.00.205 == 6.00.206 == 6.00.204 == 6.00.300
CVE-2005-4517	High	December 28, 2005 12/28/05	== 6.00.207 == 6.00.200 == 6.00.206 == 6.00.300
CVE-2005-4005	High	December 5, 2005 12/5/05	== 6.00.109
CVE-2005-3740	High	November 22, 2005 11/22/05	<= 6.00.206
CVE-2005-3157	High	October 6, 2005 10/6/05	== 6.00.109
CVE-2005-3158	High	October 6, 2005 10/6/05	== 6.00.106 == 6.00.107
CVE-2005-3160	High	October 6, 2005 10/6/05	== 6.00.105 == 6.00.106 == 6.00.103 == 6.00.101 == 6.00.107 == 6.00.104 == 6.00.100 == 6.00.108 == 6.00.102 == 6.00.109
CVE-2005-3161	High	October 6, 2005 10/6/05	== 6.00.105 == 6.00.106 == 6.00.103 == 6.00.101 == 6.00.107 == 6.00.104 == 6.00.100 == 6.00.108 == 6.00.102 == 6.00.109
CVE-2005-2783	Low	September 2, 2005 9/2/05	== 4.01 == 6.0.105 == 4.00 == 6.0.106 == 5.0 == 5.01_service_pack == 6.0.107
CVE-2005-2401	Medium	July 27, 2005 7/27/05	== 4.01 == 6.0.105 == 4.00 == 6.0.106 == 5.0 == 5.01_service_pack
CVE-2005-2074	Low	June 29, 2005 6/29/05	== 6.0.105
CVE-2005-2075	Medium	June 29, 2005 6/29/05	== 5.0 == 6.0
CVE-2005-0345	Medium	May 2, 2005 5/2/05	== 4.0
CVE-2005-0829	Low	May 2, 2005 5/2/05	== 5.01
CVE-2005-0692	Low	March 6, 2005 3/6/05	== 5.0
CVE-2004-1723	Medium	December 31, 2004 12/31/04	== 4.00
CVE-2004-2437	High	December 31, 2004 12/31/04	== 4.01
CVE-2004-2438	Low	December 31, 2004 12/31/04	== 4.01
CVE-2004-1724	High	August 18, 2004 8/18/04	== 4.0

php-fusion / php-fusion

58 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-3172	High	February 17, 2023 2/17/23	>= 9.03.90 < 9.10.00
CVE-2020-23702	Low	July 7, 2021 7/7/21	== 9.03.60
CVE-2020-23178	Medium	July 2, 2021 7/2/21	== 9.03.50
CVE-2020-23179	Medium	July 2, 2021 7/2/21	== 9.03.50
CVE-2020-23181	Medium	July 2, 2021 7/2/21	== 9.03.60
CVE-2020-23182	Medium	July 2, 2021 7/2/21	== 9.03.60
CVE-2020-23184	Medium	July 2, 2021 7/2/21	== 9.03.60
CVE-2020-23185	Medium	July 2, 2021 7/2/21	== 9.03.60
CVE-2020-35952	Medium	January 3, 2021 1/3/21	>= 9.0 < 9.03.90
CVE-2020-24949	High	September 3, 2020 9/3/20	== 9.03.50
CVE-2020-23658	Medium	August 26, 2020 8/26/20	== 9.03.60
CVE-2020-17449	Medium	August 12, 2020 8/12/20	>= 9.0 <= 9.03
CVE-2020-17450	Medium	August 12, 2020 8/12/20	>= 9.0 <= 9.03
CVE-2020-15041	Low	June 24, 2020 6/24/20	== 9.03.60
CVE-2020-14960	High	June 22, 2020 6/22/20	== 9.03.50
CVE-2020-12718	Medium	May 8, 2020 5/8/20	== 9.03.50
CVE-2020-12706	Medium	May 7, 2020 5/7/20	== 9.03.50
CVE-2020-12708	Medium	May 7, 2020 5/7/20	== 9.03.50
CVE-2020-12461	High	April 29, 2020 4/29/20	== 9.03.50
CVE-2020-12438	Medium	April 28, 2020 4/28/20	== 9.03.50
CVE-2019-12099	High	May 14, 2019 5/14/19	< 9.03.00
CVE-2015-8375	Low	September 25, 2017 9/25/17	== 9.00
CVE-2014-8596	High	November 17, 2014 11/17/14	== 7.02.07
CVE-2013-7375	High	May 5, 2014 5/5/14	== 7.02.03 == 7.02.05 == 7.02.01 == 7.02.02 == 7.02.04
CVE-2013-1803	High	May 5, 2014 5/5/14	<= 7.02.05 == 7.02.03 == 7.02.01 == 7.02.02 == 7.02.04
CVE-2013-1806	Medium	April 30, 2014 4/30/14	<= 7.02.05 == 7.02.03 == 7.02.01 == 7.02.02 == 7.02.04
CVE-2013-1807	Medium	April 30, 2014 4/30/14	<= 7.02.05 == 7.02.03 == 7.02.01 == 7.02.02 == 7.02.04
CVE-2013-1804	Low	April 29, 2014 4/29/14	<= 7.02.05 == 7.02.03 == 7.02.01 == 7.02.02 == 7.02.04
CVE-2012-6043	Low	November 26, 2012 11/26/12	== 7.02.04
CVE-2008-6850	Low	July 7, 2009 7/7/09	== 6.01.17 == 7.00.3
CVE-2008-5946	High	January 22, 2009 1/22/09	== 4.01
CVE-2008-5335	Medium	December 5, 2008 12/5/08	== 6.01.15 == 7.00.1
CVE-2008-1918	Medium	April 23, 2008 4/23/08	== 6.01.14 == 6.00.307
CVE-2007-3559	Low	July 4, 2007 7/4/07	== 6.01.9 == 6.01.10

Showing vulnerabilities for 2 products matching "php_fusion". 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.