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.

362,127

Total vulnerabilities in the database

Vulnerabilities for products matching "fortisiem"

Found 1 matching product.

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

fortinet / fortisiem

182 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-59838	Medium	July 15, 2026 7/15/26	>= 6.4.0 < 7.2.7 >= 7.3.0 < 7.3.5 == 7.4.0
CVE-2026-59841	High	July 14, 2026 7/14/26	>= 7.4.0 < 7.4.2
CVE-2026-25972	Low	March 10, 2026 3/10/26	>= 7.3.0 < 7.3.5 == 7.4.0
CVE-2025-64155	Critical	January 13, 2026 1/13/26	>= 6.7.0 < 7.1.9 >= 7.2.0 < 7.2.7 >= 7.3.0 < 7.3.5 == 7.4.0
CVE-2025-58324	Medium	October 14, 2025 10/14/25	>= 6.2.0 < 7.2.3
CVE-2025-25256	Critical	August 12, 2025 8/12/25	>= 5.4.0 < 6.7.10 >= 7.0.0 < 7.0.4 >= 7.1.0 < 7.1.8 >= 7.2.0 < 7.2.6 >= 7.3.0 < 7.3.2
CVE-2023-40714	Critical	April 2, 2025 4/2/25	>= 6.6.0 <= 6.6.3 == 7.0.0 >= 6.4.0 <= 6.5.1 >= 6.7.0 <= 6.7.3
CVE-2019-17659	Low	March 17, 2025 3/17/25	< 5.2.7
CVE-2024-55592	Low	March 11, 2025 3/11/25	>= 5.3.0 <= 7.2.5
CVE-2023-40723	High	March 11, 2025 3/11/25	>= 5.1.0 < 6.4.2 >= 6.5.0 < 6.5.2 >= 6.6.0 < 6.6.4 >= 6.7.0 < 6.7.5
CVE-2024-27780	Low	February 11, 2025 2/11/25	>= 6.7.0 <= 6.7.9 >= 7.0.0 <= 7.0.3 >= 7.1.0 <= 7.1.8
CVE-2024-52969	Low	January 14, 2025 1/14/25	>= 6.4.0 <= 7.1.7
CVE-2024-46667	High	January 14, 2025 1/14/25	>= 6.3.0 <= 6.3.3 >= 6.1.0 <= 6.1.2 == 5.4.0 >= 5.3.0 <= 5.3.3 >= 6.2.0 <= 6.2.1 >= 6.4.0 <= 6.4.4 >= 7.0.0 <= 7.0.3 >= 6.7.0 <= 6.7.9 >= 6.6.0 <= 6.6.5 >= 6.5.0 <= 6.5.3 >= 7.1.0 < 7.1.6
CVE-2024-23109	Critical	February 5, 2024 2/5/24	>= 6.6.0 <= 6.6.3 == 7.1.1 == 7.1.0 >= 7.0.0 <= 7.0.2 >= 6.7.0 <= 6.7.8 >= 6.5.0 <= 6.5.2 >= 6.4.0 <= 6.4.2
CVE-2024-23108	Critical	February 5, 2024 2/5/24	>= 6.6.0 <= 6.6.3 == 7.1.1 == 7.1.0 >= 7.0.0 <= 7.0.2 >= 6.7.0 <= 6.7.8 >= 6.5.0 <= 6.5.2 >= 6.4.0 <= 6.4.2
CVE-2023-45585	Low	November 14, 2023 11/14/23	== 6.4.1 == 6.4.0 == 6.2.1 == 6.2.0 == 5.4.0 >= 5.3.0 <= 5.3.3 == 6.6.0 == 6.6.1 == 6.6.2 == 6.6.3 == 6.5.0 == 6.5.1 == 6.4.2 == 6.1.0 == 6.1.1 == 6.1.2 == 7.0.0 == 6.3.0 == 6.3.1 == 6.3.2 == 6.3.3 >= 6.7.0 <= 6.7.6
CVE-2023-41676	Low	November 14, 2023 11/14/23	>= 6.7.0 <= 6.7.5 == 7.0.0
CVE-2023-36553	Critical	November 14, 2023 11/14/23	== 5.2.5 == 5.4.0 == 5.2.2 == 5.2.1 >= 5.1.0 <= 5.1.3 == 5.0.0 == 5.0.1 == 5.2.6 == 5.2.7 == 5.2.8 == 4.9.0 == 4.7.2 == 4.10.0 == 5.3.0 == 5.3.1 == 5.3.2 == 5.3.3
CVE-2023-34992	Critical	October 10, 2023 10/10/23	== 6.4.1 == 6.4.0 == 6.5.0 == 6.5.1 == 6.4.2 >= 6.6.0 <= 6.6.3 >= 6.7.0 <= 6.7.5 == 7.0.0
CVE-2023-36551	Low	September 13, 2023 9/13/23	>= 6.7.0 < 6.7.6
CVE-2023-26204	Low	June 13, 2023 6/13/23	== 6.4.1 == 6.4.0 >= 6.3.0 <= 6.3.3 == 6.2.1 == 6.2.0 == 5.4.0 >= 5.3.0 <= 5.3.3 == 6.5.0 == 6.5.1 == 6.4.2 == 6.1.0 == 6.1.1 == 6.1.2 >= 6.6.0 <= 6.6.3 >= 6.7.0 <= 6.7.5
CVE-2022-43949	Medium	June 13, 2023 6/13/23	== 6.4.1 == 6.4.0 >= 6.3.0 <= 6.3.3 == 6.2.1 == 6.2.0 == 5.4.0 >= 5.3.0 <= 5.3.3 == 6.7.0 == 6.5.0 == 6.5.1 == 6.4.2 == 6.1.0 == 6.1.1 == 6.1.2 == 6.7.1 >= 6.6.0 <= 6.6.3
CVE-2022-42478	High	June 13, 2023 6/13/23	== 5.2.5 == 6.4.1 == 6.4.0 >= 6.3.0 <= 6.3.3 == 6.2.1 == 6.2.0 == 5.4.0 >= 5.3.0 <= 5.3.3 == 5.2.2 == 5.2.1 >= 5.1.0 <= 5.1.3 == 6.7.0 == 6.6.0 == 6.6.1 == 6.6.2 == 6.6.3 == 6.5.0 == 6.5.1 == 6.4.2 == 5.2.6 == 5.2.7 == 5.2.8 == 6.1.0 == 6.1.1 == 6.1.2
CVE-2022-26119	High	November 2, 2022 11/2/22	== 6.4.1 == 6.4.0 >= 6.3.0 <= 6.3.3 == 6.2.1 == 6.2.0 >= 6.1.0 <= 6.1.2 == 5.4.0 >= 5.3.0 <= 5.3.3 >= 5.2.5 <= 5.2.8 == 5.2.2 == 5.2.1 >= 5.1.0 <= 5.1.3 == 5.0.0 == 5.0.1
CVE-2021-41022	High	November 2, 2021 11/2/21	>= 3.1.0 <= 4.1.4
CVE-2021-41023	Medium	November 2, 2021 11/2/21	>= 3.1.0 <= 4.1.4
CVE-2019-17653	High	March 12, 2020 3/12/20	== 5.2.5
CVE-2019-17651	Medium	January 28, 2020 1/28/20	<= 5.2.5
CVE-2019-16153	Critical	January 23, 2020 1/23/20	>= 5.0.0 <= 5.2.5
CVE-2019-6700	Medium	January 7, 2020 1/7/20	< 5.2.5
CVE-2018-13378	Low	April 17, 2019 4/17/19	<= 5.2.0

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.