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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "liferay_portal"

Found 1 matching product.

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

liferay / liferay_portal

519 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2021-38263	Medium	March 3, 2022 3/3/22	<= 7.3.2
CVE-2021-38264	Medium	March 3, 2022 3/3/22	== 7.4.0 == 7.4.1
CVE-2021-38266	High	March 2, 2022 3/2/22	<= 7.2.1
CVE-2021-38268	Medium	March 2, 2022 3/2/22	>= 7.0.0 < 7.3.7
CVE-2020-28884	High	January 28, 2022 1/28/22	== 7.2-ga1 == 7.3.5-ga6
CVE-2020-28885	High	January 28, 2022 1/28/22	== 7.2-ga1 == 7.3.5-ga6
CVE-2021-33337	Medium	August 4, 2021 8/4/21	>= 7.3.0 <= 7.3.4
CVE-2021-33338	High	August 4, 2021 8/4/21	>= 7.1.0 <= 7.3.2
CVE-2021-35463	Medium	August 4, 2021 8/4/21	== 7.4.0
CVE-2021-33336	Medium	August 4, 2021 8/4/21	>= 7.3.0 < 7.3.4
CVE-2021-33339	Low	August 4, 2021 8/4/21	>= 7.2.1 < 7.3.5
CVE-2021-33335	High	August 3, 2021 8/3/21	>= 7.0.3 < 7.3.5
CVE-2021-33331	Medium	August 3, 2021 8/3/21	>= 7.0.0 < 7.3.2
CVE-2021-33332	Medium	August 3, 2021 8/3/21	>= 7.1.0 < 7.3.3
CVE-2021-33333	Medium	August 3, 2021 8/3/21	< 7.3.3
CVE-2021-33334	Low	August 3, 2021 8/3/21	>= 7.0.0 < 7.3.3
CVE-2021-33320	Low	August 3, 2021 8/3/21	< 7.3.1
CVE-2021-33321	High	August 3, 2021 8/3/21	>= 6.2.3 < 7.3.3
CVE-2021-33322	High	August 3, 2021 8/3/21	< 7.3.1
CVE-2021-33323	High	August 3, 2021 8/3/21	>= 7.1.0 < 7.3.1
CVE-2021-33324	Low	August 3, 2021 8/3/21	>= 7.1.0 < 7.3.2
CVE-2021-33325	Low	August 3, 2021 8/3/21	< 7.3.3
CVE-2021-33326	Medium	August 3, 2021 8/3/21	< 7.3.5
CVE-2021-33327	Low	August 3, 2021 8/3/21	>= 7.2.0 < 7.3.4
CVE-2021-33328	Medium	August 3, 2021 8/3/21	>= 7.0.0 < 7.3.5
CVE-2021-33330	Low	August 3, 2021 8/3/21	>= 7.2.0 < 7.3.3
CVE-2021-29048	Medium	May 17, 2021 5/17/21	== 7.3.4 == 7.3.5
CVE-2021-29051	Medium	May 17, 2021 5/17/21	>= 7.2.0 <= 7.3.5
CVE-2021-29052	Low	May 17, 2021 5/17/21	>= 7.3.0 <= 7.3.5
CVE-2021-29043	Medium	May 17, 2021 5/17/21	>= 7.0.0 <= 7.3.5
CVE-2021-29044	Medium	May 17, 2021 5/17/21	>= 7.0.0 <= 7.3.5
CVE-2021-29045	Medium	May 17, 2021 5/17/21	>= 7.3.2 <= 7.3.5
CVE-2021-29046	Medium	May 17, 2021 5/17/21	== 7.3.5
CVE-2021-29053	High	May 17, 2021 5/17/21	== 7.3.5
CVE-2021-29040	Medium	May 16, 2021 5/16/21	<= 7.3.4
CVE-2021-29047	High	May 16, 2021 5/16/21	== 7.3.4 == 7.3.5
CVE-2021-29039	Medium	May 16, 2021 5/16/21	== 7.3.4
CVE-2020-25476	Medium	January 7, 2021 1/7/21	== 7.1.3 == 7.2.1
CVE-2020-15840	Medium	September 24, 2020 9/24/20	== 6.2 < 7.3.1
CVE-2020-15839	Medium	September 22, 2020 9/22/20	< 7.3.3
CVE-2020-24554	High	September 1, 2020 9/1/20	< 7.3.3
CVE-2020-15841	High	July 20, 2020 7/20/20	< 7.3.0
CVE-2020-15842	High	July 20, 2020 7/20/20	< 7.3.0
CVE-2020-13444	Medium	June 10, 2020 6/10/20	== 7.1.1-ga2 == 7.1-ga1 == 7.1-ga2 == 7.1-ga3 == 7.2-ga1 == 7.3-ga2 == 7.3-ga1
CVE-2020-13445	High	June 10, 2020 6/10/20	== 7.1.1-ga2 == 7.1-ga1 == 7.1-ga2 == 7.1-ga3 == 7.2-ga1 == 7.3-ga2 == 7.3-ga1
CVE-2020-7961	Critical	March 20, 2020 3/20/20	< 7.2.1
CVE-2020-7934	Medium	January 28, 2020 1/28/20	>= 7.1.0 <= 7.2.1
CVE-2019-16891	Critical	October 4, 2019 10/4/19	== 7.1.0-a1 == 7.1.0-a2 == 7.1.0-b1 == 7.1.0-b2 == 7.1.0-b3 == 7.1.0-ga1 == 7.1.0-m1 == 7.1.0-m2 == 7.1.0-rc1 == 7.0.6-ga7 == 7.0.5-ga6 == 7.0.4-ga5 == 7.0.3-ga4 == 7.0.2-ga3 == 7.0.1-ga2 == 7.0.0-a1 == 7.0.0-a2 == 7.0.0-a3 == 7.0.0-a4 == 7.0.0-a5 == 7.0.0-b1 == 7.0.0-b2 == 7.0.0-b3 == 7.0.0-b4 == 7.0.0-b5 == 7.0.0-b6 == 7.0.0-b7 == 7.0.0-ga1 == 7.0.0-m1 == 7.0.0-m2 == 7.0.0-m3 == 7.0.0-m4 == 7.0.0-m5 == 7.0.0-m6 == 7.0.0-m7 == 6.2.5-ga6 == 6.2.4-ga5 == 6.2.3-ga4 == 6.2.2-ga3 == 6.2.1-ga2 == 6.2.0-b1 == 6.2.0-b2 == 6.2.0-ga1 == 6.2.0-m1 == 6.2.0-m2 == 6.2.0-m3 == 6.2.0-m4 == 6.2.0-m5 == 6.2.0-m6 == 6.2.0-rc1 == 6.2.0-rc2 == 6.2.0-rc3 == 6.2.0-rc4 == 6.2.0-rc5 == 6.2.0-rc6 == 6.1.2-ga3 == 6.1.1-ga2 == 6.1.0-b1 == 6.1.0-b2 == 6.1.0-b3 == 6.1.0-b4 == 6.1.0-ga1 == 6.1.0-rc1 <= 6.0.6 == 7.1.1-ga2 == 7.1.2-ga3 == 7.1.3-ga4 == 7.2.0-alpha1 == 7.2.0-beta1 == 7.2.0-beta2 == 7.2.0-beta3 == 7.2.0-rc2 == 7.2.0-rc3 == 7.2.0-m2 == 7.2.0-rc1
CVE-2019-16147	Medium	September 9, 2019 9/9/19	< 7.2.0 == 7.2.0-alpha1 == 7.2.0-beta1 == 7.2.0-beta2 == 7.2.0-beta3 == 7.2.0-rc2 == 7.2.0-rc3 == 7.2.0-milestone2 == 7.2.0-ga1
CVE-2019-6588	Low	June 3, 2019 6/3/19	== 7.1.0-a1 == 7.1.0-a2 == 7.1.0-b1 == 7.1.0-b2 == 7.1.0-b3 == 7.1.0-ga1 == 7.1.0-m1 == 7.1.0-m2 == 7.1.0-rc1 == 7.0.6-ga7 == 7.0.5-ga6 == 7.0.4-ga5 == 7.0.3-ga4 == 7.0.2-ga3 == 7.0.1-ga2 == 7.0.0-a1 == 7.0.0-a2 == 7.0.0-a3 == 7.0.0-a4 == 7.0.0-a5 == 7.0.0-b1 == 7.0.0-b2 == 7.0.0-b3 == 7.0.0-b4 == 7.0.0-b5 == 7.0.0-b6 == 7.0.0-b7 == 7.0.0-ga1 == 7.0.0-m1 == 7.0.0-m2 == 7.0.0-m3 == 7.0.0-m4 == 7.0.0-m5 == 7.0.0-m6 == 7.0.0-m7 == 6.2.5-ga6 == 6.2.4-ga5 == 6.2.3-ga4 == 6.2.2-ga3 == 6.2.1-ga2 == 6.2.0-b1 == 6.2.0-b2 == 6.2.0-ga1 == 6.2.0-m1 == 6.2.0-m2 == 6.2.0-m3 == 6.2.0-m4 == 6.2.0-m5 == 6.2.0-m6 == 6.2.0-rc1 == 6.2.0-rc2 == 6.2.0-rc3 == 6.2.0-rc4 == 6.2.0-rc5 == 6.2.0-rc6 == 6.1.2-ga3 == 6.1.1-ga2 == 6.1.0-b1 == 6.1.0-b2 == 6.1.0-b3 == 6.1.0-b4 == 6.1.0-ga1 == 6.1.0-rc1 <= 6.0.6

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.