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

Found 1 matching product.

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

sap / netweaver

90 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-23685	Low	February 10, 2026 2/10/26	== 7.50
CVE-2025-42968	Medium	July 8, 2025 7/8/25	== 700 == 701 == 702 == 710 == 731 == 740 == 750 == 751 == 752 == 753 == 754 == 755 == 756 == 757 == 758 == 816 == 914 == 916
CVE-2025-42999	Critical	May 13, 2025 5/13/25	== 7.5
CVE-2025-31324	Critical	April 24, 2025 4/24/25	== 7.50
CVE-2024-27898	Medium	April 9, 2024 4/9/24	== 7.5
CVE-2024-25644	Medium	March 12, 2024 3/12/24	== 7.50
CVE-2024-22124	Low	January 9, 2024 1/9/24	== krnl64nuc_7.22 == kernel_7.22 == krnl64uc_7.22ext == krnl64uc_7.53 == krnl64nuc_7.22ext == webdisp_7.22ext == webdisp_7.53 == webdisp_7.54 == kernel_7.53 == kernel_7.54
CVE-2023-41367	Medium	September 12, 2023 9/12/23	== 7.50
CVE-2023-36922	Critical	July 11, 2023 7/11/23	== 600 == 602 == 603 == 604 == 605 == 606 == 617 == 618 == 800 == 802 == 803 == 804 == 805 == 806 == 807
CVE-2023-32114	Low	June 13, 2023 6/13/23	== 702 == 731 == 740 == 750 == 751 == 752 == 753 == 754 == 755 == 756 == 757
CVE-2023-33985	Medium	June 13, 2023 6/13/23	== 7.50
CVE-2023-33984	Medium	June 13, 2023 6/13/23	== 7.50
CVE-2023-29186	High	April 11, 2023 4/11/23	== 707 == 737 == 747 == 757
CVE-2023-27499	Medium	April 11, 2023 4/11/23	== 7.22ext
CVE-2023-0021	Medium	March 14, 2023 3/14/23	== 701 == 702 == 700 == 731 == 740 == 750
CVE-2022-28217	Medium	June 13, 2022 6/13/22	== 7.30 == 7.31 == 7.40 == 7.20 == 7.50
CVE-2022-28772	High	April 12, 2022 4/12/22	== 7.53 == krnl64nuc_7.22 == 7.22ext == 7.49 == krnl64uc_7.22 == kernel_7.22 == 7.77 == 7.81 == 7.85 == 7.86
CVE-2022-28773	High	April 12, 2022 4/12/22	== 7.53 == krnl64nuc_7.22 == 7.22ext == 7.49 == krnl64uc_7.22 == kernel_7.22 == 7.77 == 7.81 == 7.85 == 7.86
CVE-2022-22534	Medium	February 9, 2022 2/9/22	== 701 == 702 == 700 == 731 == 740 == 750 == 751 == 752 == 753 == 754 == 755 == 756
CVE-2021-38183	Medium	October 12, 2021 10/12/21	== 701 == 702 == 730 == 700
CVE-2021-38163	Critical	September 14, 2021 9/14/21	== 7.30 == 7.31 == 7.40 == 7.50
CVE-2021-21481	High	March 9, 2021 3/9/21	== 7.30 == 7.11 == 7.31 == 7.40 == 7.20 == 7.10 == 7.50
CVE-2020-6285	Medium	July 14, 2020 7/14/20	== 7.30 == 7.11 == 7.31 == 7.40 == 7.20 == 7.10 == 7.50
CVE-2020-6203	Critical	March 10, 2020 3/10/20	== 7.30 == 7.11 == 7.31 == 7.40 == 7.20 == 7.10 == 7.50
CVE-2020-6185	Medium	February 12, 2020 2/12/20	== 7.40
CVE-2020-6181	Medium	February 12, 2020 2/12/20	== 7.30 == 7.31 == 7.02 == 7.40
CVE-2020-6184	Medium	February 12, 2020 2/12/20	== 7.40
CVE-2011-1517	Critical	February 5, 2020 2/5/20	== 7.0
CVE-2013-1593	High	January 23, 2020 1/23/20	== 2004s == 7.01-sr1 == 7.02-sp06 == 7.30-sp04
CVE-2013-1592	Critical	January 23, 2020 1/23/20	== 2004s == 7.01-sr1 == 7.02-sp06 == 7.30-sp04
CVE-2019-0351	Medium	August 14, 2019 8/14/19	== 7.30 == 7.31 == 7.40 == 7.20 == 7.10 == 7.50
CVE-2019-0248	Medium	January 8, 2019 1/8/19	== 7.5 == 7.53 == 7.52 == 7.51
CVE-2018-2476	Medium	November 13, 2018 11/13/18	== 7.30 == 7.31 == 7.40
CVE-2018-2477	Medium	November 13, 2018 11/13/18	== 7.30 == 7.31 == 7.40 == 7.50
CVE-2018-2470	Low	October 9, 2018 10/9/18	== 7.30 == 7.31 == 7.40 >= 7.0 <= 7.02 >= 7.50 <= 7.53
CVE-2018-2464	Low	September 11, 2018 9/11/18	== 7.30 == 7.31 == 7.40 == 7.20 == 7.50
CVE-2018-2462	Medium	September 11, 2018 9/11/18	== 7.31 == 7.40 == 7.41 == 7.50 == 7.30
CVE-2018-2434	Low	July 10, 2018 7/10/18	== 7.0
CVE-2015-7241	High	September 6, 2017 9/6/17	<= 7.0
CVE-2017-9844	High	July 12, 2017 7/12/17	== 7400.12.21.30308
CVE-2017-9845	High	July 12, 2017 7/12/17	== 7.40
CVE-2016-10311	High	April 10, 2017 4/10/17	== 7.3 == 7.4 == 7.0-ehp2 == 7.0-ehp1 == 7.3-ehp1 == 7.0 == 7.5 == 7.0-ehp3
CVE-2017-5372	Medium	January 23, 2017 1/23/17	*
CVE-2016-7437	Low	October 13, 2016 10/13/16	== 7.40
CVE-2016-3635	Medium	October 13, 2016 10/13/16	== 7.40
CVE-2016-7435	High	October 5, 2016 10/5/16	== 7.40-sp12
CVE-2016-4551	Medium	October 5, 2016 10/5/16	== 2004s
CVE-2016-4015	Medium	April 14, 2016 4/14/16	== 7.1 == 7.2 == 7.3 == 7.4
CVE-2016-4014	High	April 14, 2016 4/14/16	== 7.4
CVE-2016-2389	High	February 16, 2016 2/16/16	== 7.40

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.