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

Found 3 matching products. Filters apply to all results.

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

bea / weblogic_server

149 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2006-2468	Low	May 19, 2006 5/19/06	== 8.1 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp3 == 7.0-sp2 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1 == 8.1-sp1
CVE-2006-2469	High	May 19, 2006 5/19/06	== 6.1-sp4 == 8.1 == 6.1-sp5 == 9.0 == 7.0-sp4 == 7.0 == 6.1-sp3 == 7.0-sp3 == 8.1-sp3 == 7.0-sp2 == 7.0-sp5 == 6.1-sp1 == 6.0-sp6 == 8.1-sp2 == 6.1 == 7.0-sp1 == 8.1-sp1 == 8.1-sp4 == 6.1-sp2
CVE-2006-2470	High	May 19, 2006 5/19/06	== 9.0
CVE-2006-2471	Medium	May 19, 2006 5/19/06	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2006-2472	Low	May 19, 2006 5/19/06	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 9.0 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 8.1-sp5 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 9.1 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2006-1351	Medium	March 22, 2006 3/22/06	== 6.1-sp4 == 6.1-sp5 == 6.1-sp6 == 6.1-sp3 == 6.1-sp1 == 6.1 == 6.1-sp2 == 6.1-sp7
CVE-2006-1352	Medium	March 22, 2006 3/22/06	== 8.1 == 8.1-sp4 == 7.0-sp2 == 6.1 == 6.1-sp1 == 6.1-sp4 == 6.1-sp6 == 6.1-sp7 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0-sp3 == 7.0-sp5 == 6.1-sp5 == 7.0-sp1 == 7.0-sp4 == 6.1-sp3 == 8.1-sp2 == 7.0-sp6
CVE-2006-0419	Medium	January 25, 2006 1/25/06	== 7.0-sp2 == 9.0 == 7.0-sp4 == 8.1-sp5 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2006-0420	Medium	January 25, 2006 1/25/06	== 7.0-sp2 == 7.0-sp4 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2006-0421	Low	January 25, 2006 1/25/06	== 6.1 == 7.0
CVE-2006-0422	Medium	January 25, 2006 1/25/06	== 7.0-sp2 == 6.1-sp4 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2006-0424	Low	January 25, 2006 1/25/06	== 7.0-sp2 == 6.1-sp4 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2006-0426	High	January 25, 2006 1/25/06	== 8.1-sp3 == 8.1-sp4 == 8.1-sp1 == 8.1-sp2
CVE-2006-0427	Low	January 25, 2006 1/25/06	== 9.0-sp3 == 9.0-sp1 == 8.1-sp5 == 8.1-sp3 == 9.0-sp5 == 9.0-sp2 == 8.1-sp4 == 8.1-sp1 == 8.1-sp2 == 9.0-sp4
CVE-2006-0429	Low	January 25, 2006 1/25/06	== 9.0
CVE-2006-0430	Medium	January 25, 2006 1/25/06	== 7.0-sp2 == 7.0-sp4 == 9.0-sp3 == 9.0-sp1 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 9.0-sp5 == 9.0-sp2 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 9.0-sp4 == 7.0-sp1
CVE-2006-0431	Low	January 25, 2006 1/25/06	== 8.1-sp5
CVE-2006-0432	Low	January 25, 2006 1/25/06	== 9.0
CVE-2005-4704	Medium	December 31, 2005 12/31/05	== 6.1-sp4 == 8.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 7.0 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 7.0-sp2 == 7.0-sp5 == 6.1-sp1 == 8.1-sp2 == 6.1 == 7.0-sp1 == 8.1-sp1 == 6.1-sp2
CVE-2005-4705	Medium	December 31, 2005 12/31/05	== 7.0-sp2 == 6.1-sp4 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2005-4749	Medium	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2005-4750	High	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 6.1-sp4 == 7.0-sp7 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 8.1-sp5 == 6.1-sp8 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4751	Medium	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 9.0 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 6.1-sp2 == 7.0-sp1
CVE-2005-4752	Low	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4753	Medium	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp6 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4754	Medium	December 31, 2005 12/31/05	== 8.1 == 8.1-sp3 == 8.1-sp1 == 8.1-sp2
CVE-2005-4755	Low	December 31, 2005 12/31/05	== 8.1 == 8.1-sp3 == 8.1-sp1 == 8.1-sp2
CVE-2005-4756	High	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp3 == 8.1-sp4 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4757	High	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp3 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4758	Low	December 31, 2005 12/31/05	== 8.1 == 8.1-sp3 == 8.1-sp1 == 8.1-sp2
CVE-2005-4759	Medium	December 31, 2005 12/31/05	== 8.1 == 7.0
CVE-2005-4760	Medium	December 31, 2005 12/31/05	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp3 == 7.0-sp5 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4761	Low	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4762	High	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp6 == 6.1-sp7 == 6.1-sp3 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4763	High	December 31, 2005 12/31/05	== 8.1-sp4 == 6.1-sp4 == 7.0-sp7 == 8.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 7.0 == 6.1-sp3 == 6.1-sp8 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 8.1-sp5 == 6.1-sp2 == 8.1-sp3 == 7.0-sp2 == 6.1-sp1 == 7.0-sp5 == 6.1-sp7 == 6.1 == 8.1-sp2 == 7.0-sp1
CVE-2005-4764	High	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 6.1-sp4 == 7.0-sp7 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.1-sp7 == 6.1-sp3 == 8.1-sp5 == 6.1-sp8 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4765	High	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4766	Medium	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp1 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-4767	Medium	December 31, 2005 12/31/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0-sp4 == 7.0 == 8.1-sp5 == 7.0-sp6 == 7.0-sp3 == 8.1-sp1 == 8.1-sp3 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2005-2092	Low	July 5, 2005 7/5/05	== 8.1-sp1
CVE-2005-1742	Medium	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1743	High	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1745	Low	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1746	Medium	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1747	Medium	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1748	Medium	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1749	Medium	May 24, 2005 5/24/05	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp3 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2005-1744	Critical	May 24, 2005 5/24/05	<= 7.0
CVE-2005-1380	Medium	May 3, 2005 5/3/05	== 8.1 == 8.1-sp4 == 8.1-sp1 == 8.1-sp3 == 8.1-sp2
CVE-2005-0432	Medium	May 2, 2005 5/2/05	== 8.1-sp3 == 7.0-sp5

oracle / weblogic_server

306 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2022-21441	High	April 19, 2022 4/19/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-24839	High	April 11, 2022 4/11/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-22965	Critical	April 1, 2022 4/1/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-36518	High	March 11, 2022 3/11/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-23437	Medium	January 24, 2022 1/24/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21371	High	January 19, 2022 1/19/22	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21386	Medium	January 19, 2022 1/19/22	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21350	Medium	January 19, 2022 1/19/22	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21353	Medium	January 19, 2022 1/19/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21361	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21347	Medium	January 19, 2022 1/19/22	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21306	Critical	January 19, 2022 1/19/22	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21292	High	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21252	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21257	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21258	Medium	January 19, 2022 1/19/22	== 14.1.1.0.0
CVE-2022-21259	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21260	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21261	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-21262	Medium	January 19, 2022 1/19/22	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-23302	High	January 18, 2022 1/18/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-23305	Critical	January 18, 2022 1/18/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2022-23307	High	January 18, 2022 1/18/22	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-44832	Medium	December 28, 2021 12/28/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-45105	Medium	December 18, 2021 12/18/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-23450	High	December 17, 2021 12/17/21	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-4104	High	December 14, 2021 12/14/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-41182	Medium	October 26, 2021 10/26/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-41183	Medium	October 26, 2021 10/26/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-41184	Medium	October 26, 2021 10/26/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-35620	High	October 20, 2021 10/20/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-35617	Critical	October 20, 2021 10/20/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-35552	Medium	October 20, 2021 10/20/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-40690	High	September 19, 2021 9/19/21	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2403	Medium	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2397	Critical	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2394	Critical	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2382	Critical	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2376	High	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2378	High	July 21, 2021 7/21/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2351	High	July 21, 2021 7/21/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-28170	Medium	May 26, 2021 5/26/21	== 14.1.1.0.0
CVE-2021-2294	Medium	April 22, 2021 4/22/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2204	Medium	April 22, 2021 4/22/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2211	Medium	April 22, 2021 4/22/21	== 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2214	Low	April 22, 2021 4/22/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2135	Critical	April 22, 2021 4/22/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2136	Critical	April 22, 2021 4/22/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2142	Medium	April 22, 2021 4/22/21	== 10.3.6.0.0
CVE-2021-2157	High	April 22, 2021 4/22/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0

Showing vulnerabilities for 3 products matching "weblogic_server". Each product has independent pagination.

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.