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 "silverstripe"

Found 1 matching product.

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

silverstripe / silverstripe

64 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-37421	Medium	November 23, 2022 11/23/22	>= 3.0.0 < 4.11.3
CVE-2022-28803	Medium	June 29, 2022 6/29/22	< 4.10.9
CVE-2021-41559	Medium	June 28, 2022 6/28/22	< 4.10.9
CVE-2022-24444	Medium	June 28, 2022 6/28/22	== 2.5.0 <= 2.4.0
CVE-2021-28661	Low	October 7, 2021 10/7/21	>= 3.0.0 <= 3.4.1
CVE-2021-36150	Medium	October 7, 2021 10/7/21	>= 1.9.0.x <= 4.8.1 >= 1.0.0 < 1.8.1
CVE-2020-26136	Medium	June 8, 2021 6/8/21	== 4.6.0-rc1 < 4.6.0
CVE-2020-25817	Low	June 8, 2021 6/8/21	== 4.6.0-rc1 < 4.6.0
CVE-2020-26138	Medium	June 8, 2021 6/8/21	== 4.6.0-rc1 < 4.6.0
CVE-2020-6164	High	July 15, 2020 7/15/20	>= 4.5.0 < 4.5.4 >= 4.0.0 < 4.4.7 <= 3.0.0
CVE-2020-6165	Medium	July 15, 2020 7/15/20	>= 3.2.5 < 3.3.0 >= 3.2.0 < 3.2.4 >= 4.5.0 < 4.5.3
CVE-2020-9311	Medium	July 15, 2020 7/15/20	>= 3.0.0 < 3.7.5
CVE-2019-19326	Medium	July 15, 2020 7/15/20	>= 4.5.0 < 4.5.4 >= 4.0.0 < 4.4.7 >= 3.0.0 < 3.7.5
CVE-2020-9280	High	April 15, 2020 4/15/20	>= 4.0.0 <= 4.5.0
CVE-2019-12437	High	February 19, 2020 2/19/20	<= 4.3.3
CVE-2019-12246	Low	February 19, 2020 2/19/20	<= 4.3.3
CVE-2019-19325	Medium	February 17, 2020 2/17/20	>= 4.5.0 < 4.5.2 >= 4.4.0 < 4.4.5
CVE-2019-16409	Medium	September 26, 2019 9/26/19	>= 3.0.0 <= 3.7.4
CVE-2019-12617	Low	September 26, 2019 9/26/19	<= 4.3.3
CVE-2019-14272	Medium	September 26, 2019 9/26/19	<= 4.0.0
CVE-2019-14273	Medium	September 26, 2019 9/26/19	<= 4.0.0
CVE-2019-12203	Medium	September 25, 2019 9/25/19	<= 4.3.3
CVE-2019-12204	Critical	September 25, 2019 9/25/19	>= 4.1.0 <= 4.3.3
CVE-2019-12205	Medium	September 25, 2019 9/25/19	<= 4.3.3
CVE-2019-12245	Medium	September 25, 2019 9/25/19	<= 4.3.3
CVE-2019-5715	High	April 11, 2019 4/11/19	>= 4.2.0 < 4.2.4 >= 4.1.0 < 4.1.5 >= 4.0.0 < 4.0.7 >= 3.7.0 < 3.7.3 >= 3.0.0 < 3.6.7 == 4.3.0
CVE-2017-18049	Low	January 23, 2018 1/23/18	>= 3.6.0 <= 3.6.2 == 4.0.0 <= 3.5.5
CVE-2017-12849	Medium	October 12, 2017 10/12/17	== 3.6.0 <= 3.5.4
CVE-2017-14498	Low	September 15, 2017 9/15/17	<= 3.6.0
CVE-2017-5197	Low	March 6, 2017 3/6/17	== 3.5.1 <= 3.4.3 == 3.5.0
CVE-2015-8606	Low	April 13, 2016 4/13/16	== 3.2.0 <= 3.1.15
CVE-2015-5063	Low	June 24, 2015 6/24/15	== 3.1.13
CVE-2015-5062	Medium	June 24, 2015 6/24/15	== 3.1.13
CVE-2011-4958	Low	April 8, 2014 4/8/14	== 2.3.4 == 2.3.0-rc2 == 2.3.7 == 2.3.10 == 2.3.1-rc2 == 2.3.0-rc3 == 2.3.3 == 2.4.1 == 2.3.8 == 2.3.1 == 2.4.0 == 2.4.2 <= 2.3.12 == 2.3.1-rc1 == 2.4.4 == 2.3.5 == 2.3.9 == 2.4.3 == 2.3.6 == 2.3.11 == 2.3.0 == 2.3.2 == 2.3.0-rc1 == 2.4.5
CVE-2013-6789	Medium	November 13, 2013 11/13/13	== 3.0.3
CVE-2013-2653	Medium	November 13, 2013 11/13/13	== 3.0.3
CVE-2012-6458	Low	August 9, 2013 8/9/13	== 3.0.0
CVE-2012-4968	Low	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.10 == 2.3.12 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.11 == 2.3.0 == 2.3.2 == 2.4.6 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3 == 2.4.5
CVE-2010-4822	Low	September 17, 2012 9/17/12	== 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2010-4823	Low	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2010-4824	Medium	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2010-5078	Medium	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2010-5079	Medium	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2011-4959	Medium	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.10 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.11 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.4 == 2.4.3 == 2.4.5
CVE-2011-4960	High	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.10 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.11 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3 == 2.4.5
CVE-2011-4961	Medium	September 17, 2012 9/17/12	== 2.3.4 == 2.3.7 == 2.3.10 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.11 == 2.3.0 == 2.3.2 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.4 == 2.4.3 == 2.4.5
CVE-2011-4962	Medium	September 17, 2012 9/17/12	== 2.4.1 == 2.4.0 == 2.4.2 == 2.4.4 == 2.4.3 == 2.4.5
CVE-2010-5080	Medium	August 26, 2012 8/26/12	== 2.3.4 == 2.3.0-rc2 == 2.3.7 == 2.3.1-rc2 == 2.3.0-rc3 == 2.3.3 == 2.4.1 == 2.3.8 == 2.3.1 == 2.4.0 == 2.4.2 == 2.3.1-rc1 == 2.3.5 == 2.3.9 == 2.4.3 == 2.3.6 == 2.3.0 == 2.3.2 == 2.3.0-rc1
CVE-2010-5087	Medium	August 26, 2012 8/26/12	== 2.3.4 == 2.3.0-rc2 == 2.3.7 == 2.3.10 == 2.3.1-rc2 == 2.3.0-rc3 == 2.3.3 == 2.3.8 == 2.3.1 == 2.3.1-rc1 == 2.3.5 == 2.3.9 == 2.3.6 == 2.3.0 == 2.3.2 == 2.3.0-rc1 == 2.4.1 == 2.4.0 == 2.4.2 == 2.4.3
CVE-2010-5088	Medium	August 26, 2012 8/26/12	== 2.3.4 == 2.3.0-rc2 == 2.3.7 == 2.3.1-rc2 == 2.3.0-rc3 == 2.3.3 == 2.4.1 == 2.3.8 == 2.3.1 == 2.4.0 == 2.4.2 == 2.3.1-rc1 == 2.3.5 == 2.3.6 == 2.3.0 == 2.3.2 == 2.3.0-rc1

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.