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-2004-1757	Low	December 31, 2004 12/31/04	== 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-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 7.0-sp5 == 8.1-sp2 == 7.0-sp1
CVE-2004-2320	Medium	December 31, 2004 12/31/04	== 5.1-sp8 == 8.1 == 5.1-sp11 == 7.0-sp2 == 6.1-sp4 == 5.1-sp7 == 6.1 == 5.1-sp3 == 5.1-sp2 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 5.1-sp5 == 6.1-sp1 == 7.0 == 5.1-sp12 == 6.1-sp3 == 5.1-sp1 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 5.1-sp6 == 5.1-sp9 == 5.1-sp4 == 8.1-sp2 == 5.1-sp13 == 5.1-sp10 == 5.1 == 7.0-sp1
CVE-2004-2321	Low	December 31, 2004 12/31/04	== 8.1-sp1
CVE-2004-2424	Medium	December 31, 2004 12/31/04	== 8.1 == 8.1-sp4 == 8.1-sp1 == 8.1-sp3 == 8.1-sp2
CVE-2004-2696	Medium	December 31, 2004 12/31/04	== 8.1 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp6 == 7.0-sp4 == 6.1-sp1 == 7.0 == 7.0.0.1-sp1 == 6.1-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 7.0.0.1 == 7.0-sp5 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2004-0204	High	August 6, 2004 8/6/04	== 8.1 == 8.1-sp1 == 8.1-sp2
CVE-2004-0652	High	August 6, 2004 8/6/04	== 8.1 == 7.0-sp2 == 7.0.0.1-sp4 == 7.0-sp4 == 7.0 == 7.0.0.1-sp1 == 7.0-sp3 == 8.1-sp1 == 7.0.0.1 == 8.1-sp2 == 7.0.0.1-sp3 == 7.0-sp1 == 7.0.0.1-sp2
CVE-2004-0711	High	July 27, 2004 7/27/04	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp1 == 7.0-sp1
CVE-2004-0712	Low	July 27, 2004 7/27/04	== 8.1 == 8.1-sp1 == 8.1-sp2
CVE-2004-0713	Medium	July 27, 2004 7/27/04	== 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-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp2 == 7.0-sp1
CVE-2004-0715	Medium	July 27, 2004 7/27/04	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0 == 7.0-sp3 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1
CVE-2004-0470	High	July 7, 2004 7/7/04	== 8.1 == 7.0
CVE-2004-0471	Low	July 7, 2004 7/7/04	== 8.1 == 7.0
CVE-2004-1756	Medium	April 13, 2004 4/13/04	== 8.1 == 7.0-sp2 == 7.0-sp4 == 7.0-sp3 == 8.1-sp1 == 8.1-sp2 == 7.0-sp1 == 7.0
CVE-2004-1758	Low	April 13, 2004 4/13/04	== 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-sp3 == 7.0-sp3 == 8.1-sp1 == 6.1-sp2 == 8.1-sp2 == 7.0-sp1
CVE-2003-1093	Low	December 31, 2003 12/31/03	== 7.0 == 6.1-sp3 == 6.1-sp1 == 6.1 == 7.0.0.1 == 7.0-sp1 == 6.1-sp2
CVE-2003-1094	High	December 31, 2003 12/31/03	== 7.0-sp3
CVE-2003-1220	Medium	December 31, 2003 12/31/03	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp1 == 7.0 == 6.1-sp2 == 7.0.0.1-sp1 == 8.1-sp1 == 7.0.0.1 == 7.0-sp3 == 6.1-sp3 == 7.0.0.1-sp2 == 7.0-sp1 == 7.0-sp4
CVE-2003-1221	Medium	December 31, 2003 12/31/03	== 8.1 == 7.0-sp2 == 7.0 == 7.0.0.1-sp1 == 7.0-sp3 == 7.0.0.1 == 7.0.0.1-sp2 == 7.0-sp1 == 7.0-sp4 == 8.1-sp1
CVE-2003-1222	Medium	December 31, 2003 12/31/03	== 8.1 == 8.1-sp1
CVE-2003-1223	Medium	December 31, 2003 12/31/03	== 8.1 == 7.0-sp2 == 6.1-sp4 == 6.1 == 6.1-sp5 == 6.1-sp1 == 7.0 == 7.0.0.1-sp1 == 6.1-sp3 == 8.1-sp1 == 7.0.0.1 == 7.0-sp3 == 6.1-sp2 == 7.0.0.1-sp2 == 7.0-sp1 == 7.0-sp4
CVE-2003-1224	Low	December 31, 2003 12/31/03	== 7.0-sp2 == 7.0 == 7.0.0.1-sp1 == 7.0-sp3 == 7.0.0.1 == 7.0-sp1 == 7.0.0.1-sp2 == 7.0-sp4
CVE-2003-1225	Low	December 31, 2003 12/31/03	== 7.0-sp2 == 7.0 == 7.0.0.1-sp1 == 7.0.0.1 == 7.0.0.1-sp2 == 7.0-sp4 == 7.0-sp1
CVE-2003-1226	Low	December 31, 2003 12/31/03	== 7.0-sp2 == 7.0 == 7.0.0.1-sp1 == 7.0.0.1 == 7.0.0.1-sp2 == 7.0-sp1 == 7.0-sp4
CVE-2003-1290	Medium	December 31, 2003 12/31/03	== 8.1 == 8.1-sp4 == 7.0-sp2 == 7.0.0.1-sp4 == 6.1-sp4 == 6.1-sp5 == 6.0-sp1 == 6.1-sp6 == 7.0-sp4 == 6.0-sp2 == 7.0.0.1 == 7.0-sp3 == 8.1-sp3 == 6.0 == 6.1-sp2 == 6.1-sp1 == 8.1-sp1 == 7.0.0.1-sp1 == 6.1-sp3 == 7.0.0.1-sp3 == 7.0.0.1-sp2 == 7.0-sp1 == 7.0-sp5 == 8.1-sp2 == 6.1 == 7.0
CVE-2003-1437	Low	December 31, 2003 12/31/03	== 7.0.0.1-sp1 == 7.0.0.1 == 7.0-sp1 == 7.0
CVE-2003-1438	Low	December 31, 2003 12/31/03	== 7.0 == 5.1 == 6.0 == 6.1 == 7.0.0.1
CVE-2003-0621	Medium	December 1, 2003 12/1/03	== 4.2 == 5.0.1 == 5.1
CVE-2003-0622	Medium	December 1, 2003 12/1/03	== 4.2 == 5.0.1 == 5.1
CVE-2003-0623	Low	December 1, 2003 12/1/03	== 4.2 == 5.0.1 == 5.1
CVE-2003-0624	Low	December 1, 2003 12/1/03	<= 8.1 == 3.1.8
CVE-2003-0733	Medium	October 20, 2003 10/20/03	== 5.1 == 7.0
CVE-2003-0640	High	August 27, 2003 8/27/03	*
CVE-2003-0151	High	March 24, 2003 3/24/03	== 7.0-sp2 == 6.1-sp4 == 6.1 == 6.0-sp1 == 6.1-sp1 == 7.0 == 6.0 == 7.0.0.1-sp1 == 6.0-sp2 == 6.1-sp3 == 7.0.0.1-sp2 == 7.0.0.1 == 7.0-sp1 == 6.1-sp2
CVE-2003-1095	Low	March 18, 2003 3/18/03	== 7.0 == 7.0.0.1-sp1 == 7.0.0.1 == 7.0-sp1
CVE-2002-2141	High	December 31, 2002 12/31/02	== 7.0 == 7.0.0.1
CVE-2002-2142	High	December 31, 2002 12/31/02	== 6.1 == 7.0 == 6.0 == 7.0.0.1
CVE-2002-2177	Low	December 31, 2002 12/31/02	== 6.1 == 6.1-sp1 == 7.0 == 7.0.0.1
CVE-2002-1030	Low	October 4, 2002 10/4/02	== 5.1-sp11 == 5.1-sp7 == 6.1 == 5.1-sp8 == 5.1-sp2 == 6.0-sp1 == 5.1-sp5 == 6.1-sp1 == 6.0 == 6.0-sp2 == 5.1-sp12 == 5.1 == 6.1-sp3 == 5.1-sp1 == 5.1-sp6 == 5.1-sp4 == 5.1-sp3 == 5.1-sp9 == 5.1-sp10 == 6.1-sp2 == 7.0
CVE-2002-0106	Medium	March 25, 2002 3/25/02	== 6.1-sp1 == 6.1
CVE-2001-0098	High	February 12, 2001 2/12/01	<= 4.5.2
CVE-2000-1238	High	December 31, 2000 12/31/00	== 5.1-sp2 == 5.1-sp5 == 5.1 == 5.1-sp1 == 5.1-sp6 == 5.1-sp4 == 5.1-sp3
CVE-2000-0681	High	October 20, 2000 10/20/00	<= 4.5.2
CVE-2000-0682	Medium	October 20, 2000 10/20/00	== 5.1-sp11 == 5.1-sp7 == 5.1-sp8 == 5.1-sp2 == 5.1-sp5 == 5.1 == 5.1-sp9 == 5.1-sp3 == 5.1-sp12 == 5.1-sp1 == 5.1-sp6 == 5.1-sp10 == 5.1-sp4
CVE-2000-0683	Medium	October 20, 2000 10/20/00	== 5.1-sp11 == 5.1-sp7 == 5.1-sp8 == 5.1-sp2 == 5.1-sp5 == 5.1 == 5.1-sp9 == 5.1-sp3 == 5.1-sp12 == 5.1-sp1 == 5.1-sp6 == 5.1-sp10 == 5.1-sp4
CVE-2000-0684	High	October 20, 2000 10/20/00	== 4.5.1 == 3.1.8 == 4.0.4
CVE-2000-0685	High	October 20, 2000 10/20/00	== 4.5.1 == 3.1.8 == 4.0.4
CVE-2000-0500	Medium	June 21, 2000 6/21/00	== 5.1 == 3.1.8 == 4.5 == 4.0
CVE-2000-0499	High	June 8, 2000 6/8/00	* >= 3.1.8 <= 4.5.1

oracle / weblogic_server

306 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-29425	Low	April 13, 2021 4/13/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-3450	High	March 25, 2021 3/25/21	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-21347	Medium	March 23, 2021 3/23/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-21350	Medium	March 23, 2021 3/23/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-11987	High	February 24, 2021 2/24/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-27568	Medium	February 23, 2021 2/23/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-28491	High	February 18, 2021 2/18/21	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2108	Critical	January 20, 2021 1/20/21	== 12.1.3.0.0
CVE-2021-2109	High	January 20, 2021 1/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-2075	Critical	January 20, 2021 1/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-2064	Critical	January 20, 2021 1/20/21	== 12.1.3.0.0
CVE-2021-2047	Critical	January 20, 2021 1/20/21	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0
CVE-2021-2033	Low	January 20, 2021 1/20/21	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2021-2018	High	January 20, 2021 1/20/21	== 12.2.1.3.0
CVE-2021-1994	Critical	January 20, 2021 1/20/21	== 10.3.6.0.0 == 12.1.3.0.0
CVE-2021-1995	Medium	January 20, 2021 1/20/21	== 12.1.3.0.0 == 10.3.6.0.0
CVE-2021-1996	Low	January 20, 2021 1/20/21	== 10.3.6.0.0 == 12.1.3.0.0
CVE-2020-8908	Low	December 10, 2020 12/10/20	== 14.1.1.0.0
CVE-2020-13956	Medium	December 2, 2020 12/2/20	== 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14750	Critical	November 2, 2020 11/2/20	== 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-2020-14882	Critical	October 21, 2020 10/21/20	== 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-2020-14883	High	October 21, 2020 10/21/20	== 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-2020-14859	Critical	October 21, 2020 10/21/20	== 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-2020-14841	Critical	October 21, 2020 10/21/20	== 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-2020-14820	High	October 21, 2020 10/21/20	== 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-2020-14825	Critical	October 21, 2020 10/21/20	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14757	Medium	October 21, 2020 10/21/20	== 12.2.1.3.0
CVE-2020-5421	Medium	September 19, 2020 9/19/20	== 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-2020-2966	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0
CVE-2020-2967	High	July 15, 2020 7/15/20	== 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-2020-14687	Critical	July 15, 2020 7/15/20	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14652	Medium	July 15, 2020 7/15/20	== 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-2020-14639	High	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14640	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14644	Critical	July 15, 2020 7/15/20	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14645	Critical	July 15, 2020 7/15/20	== 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-2020-14636	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14637	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14638	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14622	Low	July 15, 2020 7/15/20	== 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-2020-14625	Critical	July 15, 2020 7/15/20	== 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-14588	High	July 15, 2020 7/15/20	== 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-2020-14589	High	July 15, 2020 7/15/20	== 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-2020-14572	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 10.3.6.0.0 == 12.2.1.3.0 == 12.2.1.4.0
CVE-2020-14557	Medium	July 15, 2020 7/15/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-10693	Medium	May 6, 2020 5/6/20	== 14.1.1.0.0
CVE-2020-11022	Medium	April 29, 2020 4/29/20	== 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-2020-11023	Medium	April 29, 2020 4/29/20	== 12.1.3.0.0 == 12.2.1.3.0 == 12.2.1.4.0 == 14.1.1.0.0
CVE-2020-9488	Low	April 27, 2020 4/27/20	== 10.3.6.0.0
CVE-2020-2963	High	April 15, 2020 4/15/20	== 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.