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

Found 1 matching product.

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

spip / spip

68 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-22205	High	February 26, 2026 2/26/26	< 4.4.10
CVE-2026-22206	High	February 26, 2026 2/26/26	< 4.4.10
CVE-2026-27472	Low	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.9
CVE-2026-27473	Medium	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.9
CVE-2026-27474	Medium	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.9
CVE-2026-27475	High	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.9
CVE-2026-26345	Medium	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.8
CVE-2026-26223	Medium	February 19, 2026 2/19/26	>= 4.4.0 < 4.4.8
CVE-2025-71242	Medium	February 19, 2026 2/19/26	>= 4.1.0 < 4.1.20 >= 4.2.0 < 4.2.17 >= 4.3.0 < 4.3.6
CVE-2025-71244	Medium	February 19, 2026 2/19/26	>= 4.3.0 < 4.3.9 >= 4.4.0 < 4.4.5
CVE-2025-71240	Medium	February 19, 2026 2/19/26	>= 4.2.0 < 4.2.15
CVE-2025-71241	Medium	February 19, 2026 2/19/26	>= 4.1.0 < 4.1.20 >= 4.2.0 < 4.2.17 >= 4.3.0 < 4.3.6
CVE-2023-53900	High	December 16, 2025 12/16/25	== 4.1.10
CVE-2024-53620	Low	November 26, 2024 11/26/24	== 4.3.3
CVE-2024-53619	Medium	November 26, 2024 11/26/24	== 4.3.3
CVE-2024-8517	Critical	September 6, 2024 9/6/24	== 4.3.0 == 4.3.1 >= 4.2.0 <= 4.2.15 >= 4.0.0 < 4.1.18
CVE-2024-23659	Medium	January 19, 2024 1/19/24	>= 4.2.0 < 4.2.8 < 4.1.14
CVE-2023-52322	Medium	January 4, 2024 1/4/24	>= 4.2.0 < 4.2.7 < 4.1.13
CVE-2023-27372	Critical	February 28, 2023 2/28/23	== 4.2.0-alpha2 == 4.2.0-alpha == 4.2.0 >= 4.1.0 < 4.1.8 >= 4.0.0 < 4.0.10 < 3.2.18
CVE-2023-24258	Critical	February 27, 2023 2/27/23	<= 4.1.5
CVE-2022-37155	High	December 14, 2022 12/14/22	>= 3.1.13 <= 4.1.2
CVE-2022-28959	Medium	May 19, 2022 5/19/22	<= 3.1.13
CVE-2022-28960	High	May 19, 2022 5/19/22	< 3.2.8
CVE-2022-28961	High	May 19, 2022 5/19/22	<= 3.1.13
CVE-2022-26847	Medium	March 10, 2022 3/10/22	>= 4.0.0 < 4.0.5 < 3.2.14
CVE-2022-26846	High	March 10, 2022 3/10/22	>= 4.0.0 < 4.0.5 < 3.2.14
CVE-2021-44118	Medium	January 26, 2022 1/26/22	== 4.0.0
CVE-2021-44120	Medium	January 26, 2022 1/26/22	== 4.0.0
CVE-2021-44122	High	January 26, 2022 1/26/22	== 4.0.0
CVE-2021-44123	High	January 26, 2022 1/26/22	== 4.0.0
CVE-2020-28984	Critical	November 23, 2020 11/23/20	< 3.2.8
CVE-2019-19830	Medium	December 17, 2019 12/17/19	>= 3.2.0 < 3.2.7
CVE-2019-16391	Medium	September 17, 2019 9/17/19	>= 3.2.0 < 3.2.5 < 3.1.11
CVE-2019-16392	Medium	September 17, 2019 9/17/19	>= 3.2.0 < 3.2.5 < 3.1.11
CVE-2019-16393	Medium	September 17, 2019 9/17/19	>= 3.2.0 < 3.2.5 < 3.1.11
CVE-2019-16394	Medium	September 17, 2019 9/17/19	>= 3.2.0 < 3.2.5 < 3.1.11
CVE-2019-11071	Medium	April 10, 2019 4/10/19	>= 3.2.0 < 3.2.4 >= 3.1.0 < 3.1.10
CVE-2017-15736	Low	October 22, 2017 10/22/17	<= 3.1.6
CVE-2017-9736	High	June 17, 2017 6/17/17	== 3.1.0-alpha == 3.2.0-beta == 3.1.0-rc3 == 3.1.5 == 3.1.4 == 3.1.0-rc == 3.2-alpha-1 == 3.1.0 == 3.1.3 == 3.1.1 == 3.2.0-beta2 == 3.1.0-rc2 == 3.1.2 == 3.1.0-beta
CVE-2016-7998	Medium	January 18, 2017 1/18/17	<= 3.1.2
CVE-2016-7999	Low	January 18, 2017 1/18/17	<= 3.1.2
CVE-2016-7980	Medium	January 18, 2017 1/18/17	<= 3.1.2
CVE-2016-7981	Low	January 18, 2017 1/18/17	<= 3.1.2
CVE-2016-7982	Medium	January 18, 2017 1/18/17	<= 3.1.2
CVE-2016-9997	Low	December 17, 2016 12/17/16	== 3.1.0-alpha == 3.1.0-rc3 == 3.1.0-rc == 3.1.0 == 3.1.3 == 3.1.1 == 3.1.0-rc2 == 3.1.2 == 3.1.0-beta
CVE-2016-9998	Low	December 17, 2016 12/17/16	== 3.1.0-alpha == 3.1.0-rc3 == 3.1.0-rc == 3.1.0 == 3.1.3 == 3.1.1 == 3.1.0-rc2 == 3.1.2 == 3.1.0-beta
CVE-2016-9152	Low	December 5, 2016 12/5/16	== 3.1.3
CVE-2016-3154	High	April 8, 2016 4/8/16	== 2.1.15 == 3.0.3 == 2.1.8 == 2.0.0 == 2.0.3 == 2.0.6 == 2.0.10 == 3.0.8 == 3.0.19 == 2.1.17 == 2.0.19 == 2.1.4 == 3.0.4 == 3.0.7 == 2.1.19 == 2.0.12 == 2.1.2 == 2.0.16 == 2.1.18 == 2.1.5 == 2.1.13 == 2.1.16 == 3.0.5 == 2.1.10 == 2.0.7 == 3.0.13 == 2.1.7 == 3.0.10 == 2.0.8 == 3.1.0 == 2.0.21 == 2.0.11 == 2.0.18 == 2.0.2 == 2.0.5 == 3.0.9 == 2.1.14 == 2.1.12 == 3.0.14 == 2.0.13 == 3.0.16 == 2.0.22 == 2.0.1 == 2.1.1 == 2.0.14 == 2.0.20 == 2.0.17 == 3.0.2 == 3.0.17 == 2.0.15 == 2.1.9 == 2.0.9 == 2.1.3 == 3.0.0 == 2.1.6 == 3.0.6 == 3.0.11 == 2.0.4 == 3.0.20 == 3.0.1 == 2.1.11 == 3.0.15
CVE-2016-3153	High	April 8, 2016 4/8/16	== 2.1.15 == 3.0.3 == 2.1.8 == 2.0.0 == 2.0.3 == 2.0.6 == 2.0.10 == 3.0.8 == 3.0.19 == 2.1.17 == 2.0.19 == 2.1.4 == 3.0.4 == 3.0.7 == 2.0.12 == 2.1.2 == 2.0.16 == 2.1.18 == 2.1.5 == 2.1.13 == 2.1.16 == 3.0.5 == 2.1.10 == 2.0.7 == 3.0.13 == 2.1.7 == 3.0.10 == 2.0.8 == 3.1.0 == 2.0.21 == 2.0.11 == 2.0.18 == 2.0.2 == 2.0.5 == 3.0.9 == 2.1.14 == 2.1.12 == 3.0.14 == 2.0.13 == 3.0.16 == 2.0.22 == 2.0.1 == 2.1.1 == 2.0.14 == 2.0.20 == 2.0.17 == 3.0.2 == 3.0.17 == 2.0.15 == 2.1.9 == 2.0.9 == 2.1.3 == 3.0.0 == 2.1.6 == 3.0.6 == 3.0.11 == 2.0.4 == 3.0.20 == 3.0.1 == 2.1.11 == 3.0.15
CVE-2013-7303	Low	January 30, 2014 1/30/14	== 2.1.15 == 3.0.3 == 2.0.3 == 2.0.6 == 2.0.10 == 3.0.8 == 2.1.17 == 2.0.19 == 3.0.4 == 3.0.7 == 2.1.19 == 2.0.12 == 2.1.2 == 2.0.16 == 2.1.18 == 2.1.13 == 2.1.16 == 3.0.5 == 2.1.22 == 2.1.10 == 2.0.7 == 3.0.10 == 2.1 == 2.1.23 == 2.0.8 == 2.0.21 == 2.0.11 == 2.0.18 <= 2.1.24 == 2.0.2 == 2.0.5 == 3.0.9 == 2.1.14 == 2.1.12 == 2.0.13 == 2.0.22 == 2.1.20 == 2.0.1 == 2.1.21 == 2.1.1 == 2.0.14 == 2.0.20 == 2.0.17 == 3.0.2 == 2.0.15 == 2.0.9 == 3.0.0 == 3.0.6 == 3.0.11 == 2.0.4 == 3.0.1 == 2.1.11

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.