How severe is CVE-2020-13445?

CVE-2020-13445 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-13445?

CVE-2020-13445 affects the following packages: com.liferay.portal:release.portal.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-13445?

Update com.liferay.portal:release.portal.bom to 7.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13445 is resolved across your whole dependency graph.

How do I detect CVE-2020-13445 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-13445 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2020-13445 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2020-13445, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-13445?

CVE-2020-13445 has an EPSS (Exploit Prediction Scoring System) score of 3.7%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-13445?

CVE-2020-13445 is classified as CWE-74 (CWE-74), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-13445 published, and has it been updated?

CVE-2020-13445 was published on June 10, 2020 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2020-13445 — release.portal.bom

HIGH

CVE-2020-13445 is a high-severity (CVSS 8.8) CWE-74 vulnerability in com.liferay.portal:release.portal.bom. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.liferay.portal:release.portal.bom — see the affected versions and patch details below.

Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution

Also known asGHSA-v377-8f8f-532h

Published

Jun 10, 2020

Updated

Oct 24, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Oct 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

☕com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

In Liferay Portal before 7.3.2 and Liferay DXP 7.0 before fix pack 92, 7.1 before fix pack 18, and 7.2 before fix pack 6, the template API does not restrict user access to sensitive objects, which allows remote authenticated users to execute arbitrary code via crafted FreeMarker and Velocity templates.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	all versions	7.3.2`com.liferay.portal:release.portal.bom:7.3.2`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.0.0&&< 7.0.10.fp92	7.0.10.fp92`com.liferay.portal:release.dxp.bom:7.0.10.fp92`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.1.0&&< 7.1.10.fp18	7.1.10.fp18`com.liferay.portal:release.dxp.bom:7.1.10.fp18`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.2.0&&< 7.2.10.fp6	7.2.10.fp6`com.liferay.portal:release.dxp.bom:7.2.10.fp6`

Affected Products

1 product · 7 configurations

Application

liferay portalliferay

4 versions

7.17.1.17.27.3

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

In Liferay Portal before 7.3.2 and Liferay DXP 7.0 before fix pack 92, 7…

securitylab.github.comNVDJul 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:release.portal.bom to 7.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-13445 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-13445 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-74CWE-74 CWE-862CWE-862

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Jun 10, 2020

First exploit

Jul 21, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2020-13445

GHSA-v377-8f8f-532h

References

Advisorynvd.nist.gov · CVE 2020 13445 Fixissues.liferay.com · LPE 17023 Fixportal.liferay.dev Packagegithub.com · liferay portal Evidencesecuritylab.github.com · GHSL 2020 043 liferay ce

Related vulnerabilities

This CVE is high severity; 2 of 8 other CVEs affecting release.portal.bom are rated as high or higher (top: high).

CVE-2025-62264CVE-2025-62265CVE-2025-62257CVE-2025-62266CVE-2025-62258CVE-2025-62259CVE-2025-62260CVE-2025-62261

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2020-13445 — release.portal.bom

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2020-13445 in your dependencies?