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

Found 1 matching product.

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

siemens / simatic_wincc

28 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-48363	Medium	February 13, 2024 2/13/24	== 7.4 == 7.5 == 8.0
CVE-2023-48364	Medium	February 13, 2024 2/13/24	== 7.4 == 7.5 == 8.0
CVE-2023-28829	Low	June 13, 2023 6/13/23	< 8.0
CVE-2022-24287	High	May 20, 2022 5/20/22	<= 7.4 == 7.5 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4 == 7.5-sp2_update5 == 7.5-sp2_update6 == 7.5-sp2_update7
CVE-2021-40360	High	February 9, 2022 2/9/22	== 7.4-sp1 == 7.4 == 14.0.1 == 13-sp1 == 13 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5 == 7.4-sp1_update1 == 7.4-sp1_update2 == 7.4-sp1_update3 == 7.4-sp1_update4 == 7.4-sp1_update5 == 7.4-sp1_update6 == 7.4-sp1_update7 == 7.4-sp1_update8 == 7.4-sp1_update9 == 7.4-sp1_update10 == 7.4-sp1_update11 == 7.4-sp1_update12 == 7.4-sp1_update13 < 7.4 == 15.1 == 15.1-update_1 == 15.1-update_2 == 15.1-update_3 == 15.1-update_4 == 16 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4 == 15 == 17-update1 == 17 == 16-update1 == 16-update2 == 16-update3 == 16-update4 == 13-sp2 == 7.5-sp2_update5 == 15.1-update_6 == 15.1-update_5 == 7.4-sp1_update14 == 7.4-sp1_update15 == 7.4-sp1_update16 == 7.4-sp1_update17 == 7.4-sp1_update18
CVE-2021-40363	High	February 9, 2022 2/9/22	== 7.4-sp1 == 7.4 == 7.4-update_1 == 14.0.1 == 13-sp1 == 13 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5 == 7.4-sp1_update1 == 7.4-sp1_update2 == 7.4-sp1_update3 == 7.4-sp1_update4 == 7.4-sp1_update5 == 7.4-sp1_update6 == 7.4-sp1_update7 == 7.4-sp1_update8 == 7.4-sp1_update9 == 7.4-sp1_update10 == 7.4-sp1_update11 == 7.4-sp1_update12 == 7.4-sp1_update13 < 7.4 == 15.1 == 15.1-update_1 == 15.1-update_2 == 15.1-update_3 == 15.1-update_4 == 16 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4 == 15 == 17-update1 == 17 == 16-update1 == 16-update2 == 16-update3 == 16-update4 == 13-sp2 == 7.5-sp2_update5 == 15.1-update_6 == 15.1-update_5 == 7.4-sp1_update14 == 7.4-sp1_update15 == 7.4-sp1_update16 == 7.4-sp1_update17 == 7.4-sp1_update18
CVE-2021-40364	Medium	November 9, 2021 11/9/21	<= 7.4 == 15 == 16 == 16-update1 == 16-update2 == 16-update3 == 16-update4 == 17 == 17-update1 == 7.5 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4
CVE-2021-40358	Critical	November 9, 2021 11/9/21	== 7.4 == 7.4-sp1 == 7.4-update_1 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5 == 7.4-sp1_update1 == 7.4-sp1_update2 == 7.4-sp1_update3 == 7.4-sp1_update4 == 7.4-sp1_update5 == 7.4-sp1_update6 == 7.4-sp1_update7 == 7.4-sp1_update8 == 7.4-sp1_update9 == 7.4-sp1_update10 == 7.4-sp1_update11 == 7.4-sp1_update12 == 7.4-sp1_update13 == 15.1 == 15.1-update_1 == 15.1-update_2 == 15.1-update_3 == 15.1-update_4 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4 == 17 == 15 == 17-update1 == 16-update1 == 16-update2 == 16-update3 == 16-update4 == 15.1-update_6 == 15.1-update_5 == 7.4-sp1_update14 == 7.4-sp1_update15 == 7.4-sp1_update16 == 7.4-sp1_update17 == 7.4-sp1_update18
CVE-2021-40359	High	November 9, 2021 11/9/21	<= 7.4 == 15 == 16 == 16-update1 == 16-update2 == 16-update3 == 16-update4 == 17 == 17-update1 == 7.5 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 == 7.5-sp2 == 7.5-sp2_update1 == 7.5-sp2_update2 == 7.5-sp2_update3 == 7.5-sp2_update4
CVE-2020-10048	Medium	February 9, 2021 2/9/21	== 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2 < 7.5
CVE-2020-7580	Medium	June 10, 2020 6/10/20	< 7.4 == 7.4 == 7.4-sp1 == 7.4-sp1_update1 == 7.4-sp1_update10 == 7.4-sp1_update11 == 7.4-sp1_update12 == 7.4-sp1_update13 == 7.4-sp1_update2 == 7.4-sp1_update3 == 7.4-sp1_update4 == 7.4-sp1_update5 == 7.4-sp1_update6 == 7.4-sp1_update7 == 7.4-sp1_update8 == 7.4-sp1_update9 == 7.5 == 7.5-sp1 == 7.5-sp1_update1 == 7.5-sp1_update2
CVE-2019-19282	High	March 10, 2020 3/10/20	== 7.4-sp1 == 7.4 == 7.5.1 == 14.0.1 == 13-sp1 == 13 == 7.5 == 7.5-sp1 == 15.1 == 15.1-update_1 == 15.1-update_2 == 15.1-update_3 == 15.1-update_4 == 16 == 7.4-sp1_update_1 == 7.4-sp1_update_10 == 7.4-sp1_update_11 == 7.4-sp1_update_12 == 7.4-sp1_update_13 == 7.4-sp1_update_2 == 7.4-sp1_update_3 == 7.4-sp1_update_4 == 7.4-sp1_update_5 == 7.4-sp1_update_6 == 7.4-sp1_update_7 == 7.4-sp1_update_8 == 7.4-sp1_update_9
CVE-2019-10929	Medium	August 13, 2019 8/13/19	< 16
CVE-2019-10935	Medium	July 11, 2019 7/11/19	<= 7.2 == 13 == 13-sp2 == 14 == 14-sp1 == 15 == 7.3 == 7.3-update_1 == 7.3-update_10 == 7.3-update_11 == 7.3-update_13 == 7.3-update_4 == 7.4 == 7.4-sp1 == 7.4-update_1 == 7.5
CVE-2019-10916	High	May 14, 2019 5/14/19	== 7.4 == 7.3 <= 7.2 == 7.5
CVE-2019-10917	Medium	May 14, 2019 5/14/19	== 7.4 == 7.3 <= 7.2 == 7.5
CVE-2019-10918	High	May 14, 2019 5/14/19	== 7.4 == 7.3 <= 7.2 == 7.5
CVE-2019-10922	Critical	May 14, 2019 5/14/19	<= 7.2 == 7.3
CVE-2018-4832	High	April 24, 2018 4/24/18	== 7.4-sp1 == 7.3 == 7.4 == 7.4-sp1_upd_3 == 7.3-upd_15 == 7.2-upd_14 == 7.2 < 7.2
CVE-2017-14023	Low	November 6, 2017 11/6/17	== 7.3-update13
CVE-2017-6867	Low	May 11, 2017 5/11/17	== 7.4 == 7.3
CVE-2016-9160	Medium	December 17, 2016 12/17/16	<= 7.1
CVE-2016-7165	Medium	November 15, 2016 11/15/16	== 7.2 <= 7.0 == 7.4 == 7.3 == 7.0-sp3
CVE-2016-5744	Medium	July 22, 2016 7/22/16	== 7.2 == 7.0 == 7.0-sp2 == 7.0-sp1 == 7.0-sp3
CVE-2016-5743	High	July 22, 2016 7/22/16	<= 7.3 <= 7.4
CVE-2014-8552	Medium	November 26, 2014 11/26/14	== 7.0 == 7.0-sp1 == 7.0-sp2 == 7.0-sp3 == 7.2-1 == 7.2-2 == 7.2-3 == 7.2-4 == 7.2-5 == 7.2-6 == 7.2-7 == 7.2-8 == 7.3-1
CVE-2014-8551	High	November 26, 2014 11/26/14	== 7.0 == 7.0-sp1 == 7.0-sp2 == 7.0-sp3 == 7.2-1 == 7.2-2 == 7.2-3 == 7.2-4 == 7.2-5 == 7.2-6 == 7.2-7 == 7.2-8 == 7.3-1
CVE-2010-2772	High	July 22, 2010 7/22/10	== 6.2 == 7.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.