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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "phorum"

Found 1 matching product.

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

phorum / phorum

56 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-3622	Medium	January 22, 2020 1/22/20	< 5.2.18
CVE-2012-6659	Low	September 19, 2014 9/19/14	<= 5.2.18 == 5.2.10-rc1 == 5.2.5 == 5.2.9 == 5.2.12 == 5.2.2-beta == 5.2.15 == 5.2.14 == 5.2.7 == 5.2.6 == 5.2.4-rc2 == 5.2.3-rc1 == 5.2 == 5.2.10 == 5.2.13 == 5.2.15-a == 5.2.16 == 5.2.8 == 5.2.1 == 5.2.11 == 5.2.12-a
CVE-2012-4234	Low	September 4, 2014 9/4/14	<= 5.2.18 == 5.2.10-rc1 == 5.2.12 == 5.2.15 == 5.2.14 == 5.2 == 5.2.10 == 5.2.13 == 5.2.15-a == 5.2.16 == 5.2.1 == 5.2.11 == 5.2.12-a
CVE-2011-4561	Low	November 28, 2011 11/28/11	== 5.2.18
CVE-2011-3768	Medium	September 24, 2011 9/24/11	== 5.2.15a
CVE-2011-3392	Low	September 8, 2011 9/8/11	== 5.2.10-rc1 == 3.2.2 == 5.0.15 == 3.1.1_pre == 5.2.5 == 5.0.1_alpha <= 5.2.16 == 5.2.9 == 5.2.12 == 3.4.6 == 5.2.2-beta == 5.2.15 == 3.2.3 == 5.0.13a == 5.2.14 == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 5.1.25 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 5.1.18 == 5.2.4-rc2 == 5.2.12a == 3.1.1a == 3.4.5 == 5.2.3-rc1 == 5.0.12 == 5.0.20 == 5.1.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.2 == 5.2.10 == 5.1.21 == 5.0.0_alpha == 3.2 == 5.2.13 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 5.1.14 == 3.4.2 == 5.0.6_beta == 5.1.17 == 3.4.1 == 3.4.7 == 5.0.3_beta == 5.2.8 == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc == 5.2.11 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2011-3381	Medium	September 8, 2011 9/8/11	== 5.2.10-rc1 == 3.2.2 == 5.0.15 == 3.1.1_pre == 5.2.5 == 5.0.1_alpha == 5.2.9 == 5.2.12 == 3.4.6 == 5.2.2-beta == 3.2.3 == 5.0.13a == 5.2.14 == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 <= 5.2.15 == 3.3.2 == 3.1.1_rc2 == 5.1.25 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 5.1.18 == 5.2.4-rc2 == 5.2.12a == 3.1.1a == 3.4.5 == 5.2.3-rc1 == 5.0.12 == 5.0.20 == 5.1.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.2 == 5.2.10 == 5.1.21 == 5.0.0_alpha == 3.2 == 5.2.13 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 5.1.14 == 3.4.2 == 5.0.6_beta == 5.1.17 == 3.4.1 == 3.4.7 == 5.0.3_beta == 5.2.8 == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc == 5.2.11 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2011-3382	Low	September 8, 2011 9/8/11	== 5.2.10-rc1 == 3.2.2 == 5.0.15 == 3.1.1_pre == 5.2.5 == 5.0.1_alpha == 5.2.9 == 5.2.12 == 3.4.6 == 5.2.2-beta == 3.2.3 == 5.0.13a == 5.2.14 == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 <= 5.2.15 == 3.3.2 == 3.1.1_rc2 == 5.1.25 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 5.1.18 == 5.2.4-rc2 == 5.2.12a == 3.1.1a == 3.4.5 == 5.2.3-rc1 == 5.0.12 == 5.0.20 == 5.1.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.2 == 5.2.10 == 5.1.21 == 5.0.0_alpha == 3.2 == 5.2.13 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 5.1.14 == 3.4.2 == 5.0.6_beta == 5.1.17 == 3.4.1 == 3.4.7 == 5.0.3_beta == 5.2.8 == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc == 5.2.11 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2010-1629	Low	May 19, 2010 5/19/10	== 5.2.10-rc1 == 3.2.2 == 5.0.15 == 3.1.1_pre == 5.2.5 == 5.0.1_alpha == 5.2.9 == 5.2.12 == 3.4.6 == 5.2.2-beta == 3.2.3 == 5.0.13a == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 5.1.25 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 5.1.18 == 5.2.4-rc2 == 5.2.12a == 3.1.1a == 3.4.5 == 5.2.3-rc1 == 5.0.12 == 5.0.20 == 5.1.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.2 == 5.2.10 == 5.1.21 == 5.0.0_alpha == 3.2 == 5.2.13 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta <= 5.2.14 == 5.1.14 == 3.4.2 == 5.0.6_beta == 5.1.17 == 3.4.1 == 3.4.7 == 5.0.3_beta == 5.2.8 == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc == 5.2.11 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2009-0488	Low	February 9, 2009 2/9/09	== 3.2.2 == 5.0.15 == 3.1.1_pre == 5.2.5 == 5.0.1_alpha <= 5.2.10 == 5.2.9 == 3.4.6 == 5.2.2-beta == 3.2.3 == 5.0.13a == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 5.1.25 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 5.1.18 == 5.2.4-rc2 == 3.1.1a == 3.4.5 == 5.2.3-rc1 == 5.0.12 == 5.0.20 == 5.1.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.2 == 5.1.21 == 5.0.0_alpha == 3.2 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 5.1.14 == 3.4.2 == 5.0.6_beta == 5.1.17 == 3.4.1 == 3.4.7 == 5.0.3_beta == 5.2.8 == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2008-4513	Low	October 9, 2008 10/9/08	== 5.2.8
CVE-2008-1486	Medium	March 24, 2008 3/24/08	== 5.0.15 == 5.0.1_alpha == 5.2.2-beta == 5.0.13a == 5.0.15a == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 5.0.7a_beta == 5.0.17 == 5.0.17a == 5.1.25 == 5.0.18 == 5.0.4a_beta == 5.1.18 == 5.2.4-rc2 == 5.2.3-rc1 == 5.0.12 <= 5.2.5 == 5.0.20 == 5.1.20 == 5.2 == 5.1.21 == 5.0.0_alpha == 5.0.16 == 5.0.10 == 5.0.11 == 5.0.14a == 5.0.9 == 5.0.14 == 5.0.7_beta == 5.1.14 == 5.0.6_beta == 5.1.17 == 5.0.3_beta == 5.0.4_beta == 5.0.13 == 5.2.1 == 5.0.8_rc
CVE-2007-2338	High	April 27, 2007 4/27/07	<= 5.1.20
CVE-2007-2339	High	April 27, 2007 4/27/07	<= 5.1.20
CVE-2007-2248	Low	April 25, 2007 4/25/07	<= 5.1.21
CVE-2007-2249	Medium	April 25, 2007 4/25/07	<= 5.1.20
CVE-2007-2250	Medium	April 25, 2007 4/25/07	<= 5.1.20
CVE-2006-6968	Medium	February 6, 2007 2/6/07	<= 5.1.18
CVE-2007-0767	Medium	February 6, 2007 2/6/07	<= 5.1.17
CVE-2007-0769	Medium	February 6, 2007 2/6/07	== 5.1.18
CVE-2006-6550	High	December 14, 2006 12/14/06	== 3.2.11
CVE-2006-3611	Medium	July 18, 2006 7/18/06	== 3.2.2 <= 5.1.14 == 5.0.15 == 3.1.1_pre == 5.0.1_alpha == 3.4.6 == 3.2.3 == 5.0.13a == 5.0.15a == 3.2.7 == 3.4.3 == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.1.13 == 3.1.1 == 3.2.8 == 3.3.1a == 5.0.7a_beta == 3.4.4 == 5.0.17 == 5.0.17a == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 5.0.18 == 5.0.4a_beta == 4.3.7 == 3.0.7 == 3.1.1a == 3.4.5 == 5.0.12 == 5.0.20 == 3.4.8a == 3.2.5 == 3.2.3a == 5.0.0_alpha == 3.2 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 3.4.2 == 5.0.6_beta == 3.4.1 == 3.4.7 == 5.0.3_beta == 3.4.8 == 3.2.4 == 5.0.4_beta == 5.0.13 == 5.0.8_rc == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2006-3612	Low	July 18, 2006 7/18/06	== 5.1.14
CVE-2006-3615	Medium	July 18, 2006 7/18/06	== 5.1.14
CVE-2006-3249	High	June 27, 2006 6/27/06	<= 5.1.14
CVE-2006-3053	High	June 16, 2006 6/16/06	== 3.2.2 == 3.1.1_pre == 3.4.6 == 3.2.3 == 5.0.15a == 3.2.7 == 3.4.3 == 3.1.1 == 3.2.8 == 3.3.1a == 3.4.4 == 5.0.17a == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 5.0.18 == 3.1.1a == 3.4.5 == 5.0.12 == 3.4.8a == 3.2.5 == 3.2.3a == 3.2 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 <= 5.1.13 == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 3.4.2 == 3.4.1 == 3.4.7 == 5.0.3_beta == 3.4.8 == 3.2.4 == 5.0.13 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2005-3543	Medium	November 16, 2005 11/16/05	== 5.0.15 == 5.0.1_alpha == 5.0.13a == 5.0.2_alpha == 5.0.5_beta == 5.0.19 == 5.0.7a_beta == 5.0.17 == 5.0.18 == 5.0.4a_beta == 5.0.12 == 5.0.20 == 5.0.0_alpha == 5.0.16 == 5.0.10 == 5.0.11 == 5.0.14a == 5.0.9 == 5.0.14 == 5.0.7_beta == 5.0.6_beta == 5.0.3_beta == 5.0.4_beta == 5.0.13 == 5.0.8_rc
CVE-2005-2836	Low	September 7, 2005 9/7/05	== 3.2.2 == 5.0.15 == 3.1.1_pre == 3.4.6 == 3.2.3 == 3.2.7 == 3.4.3 == 3.1.1 == 3.2.8 == 3.3.1a == 3.4.4 == 5.0.17 == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 4.3.7 == 3.1.1a == 3.4.5 == 5.0.12 == 3.2.5 == 3.2.3a == 3.2 == 5.0.16 == 5.0.10 == 3.1.2 == 5.0.11 == 5.0.14a == 5.0.9 == 3.1 == 5.0.14 == 5.0.7_beta == 3.4.2 == 3.4.1 == 3.4.7 == 5.0.3_beta == 3.4.8 == 3.2.4 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2005-0783	Low	May 2, 2005 5/2/05	== 5.0.14
CVE-2005-0784	Low	May 2, 2005 5/2/05	== 5.0.14
CVE-2005-0843	Medium	May 2, 2005 5/2/05	== 5.0.14a
CVE-2004-2110	High	December 31, 2004 12/31/04	<= 3.4.5
CVE-2004-2240	High	December 31, 2004 12/31/04	== 5.0.11
CVE-2004-2241	Low	December 31, 2004 12/31/04	== 5.0.11
CVE-2004-2242	Low	December 31, 2004 12/31/04	== 5.0.7_beta
CVE-2004-2243	High	December 31, 2004 12/31/04	== 4.3.7
CVE-2004-1938	High	April 19, 2004 4/19/04	== 3.4.7 == 3.4.8
CVE-2004-1822	Low	March 15, 2004 3/15/04	== 3.2.2 == 3.1.1_pre == 3.4.6 == 3.2.3 == 3.2.7 == 3.4.3 == 3.1.1 == 3.2.8 == 3.3.1a == 3.4.4 == 3.3.1 == 3.4 == 3.3.2 == 3.1.1_rc2 == 3.1.1a == 3.4.5 == 3.2.5 == 3.2.3a == 3.2 == 3.1.2 == 3.1 == 3.4.2 == 3.4.1 == 5.0.3_beta == 3.2.4 == 3.2.3b == 3.3.2b3 == 3.3.2a == 3.2.6
CVE-2004-0034	Low	January 20, 2004 1/20/04	<= 3.4.5
CVE-2004-0035	High	January 20, 2004 1/20/04	<= 3.4.5
CVE-2003-1465	Medium	December 31, 2003 12/31/03	== 3.4 == 3.4.2 == 3.4.1
CVE-2003-1466	High	December 31, 2003 12/31/03	== 3.4 == 3.4.2 == 3.4.1
CVE-2003-1467	Low	December 31, 2003 12/31/03	<= 3.4.2 == 3.4 == 3.4.1
CVE-2003-1486	Medium	December 31, 2003 12/31/03	== 3.4 == 3.4.2 == 3.4.1
CVE-2003-1487	High	December 31, 2003 12/31/03	== 3.4 == 3.4.2 == 3.4.1
CVE-2003-0283	Medium	June 16, 2003 6/16/03	<= 3.4.3
CVE-2002-2340	Low	December 31, 2002 12/31/02	== 3.3.2a
CVE-2002-0764	High	August 12, 2002 8/12/02	== 3.3.2a
CVE-2002-0352	Medium	June 25, 2002 6/25/02	== 3.3.2
CVE-2000-1228	Medium	December 31, 2000 12/31/00	== 3.0.7

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.