# CVE-2020-13445: Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution

> Authenticated attackers can execute arbitrary code by injecting malicious FreeMarker or Velocity templates into the Liferay Portal template API.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-v377-8f8f-532h

## What is CVE-2020-13445?

CVE-2020-13445 is a high-severity code injection vulnerability in Liferay Liferay Portal, published on 10 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-862 (Missing Authorization), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2020-13445?

8 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.0 | 7.0.10.fp92 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.0 | 7.0.10.fp92 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp18 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 | 7.1.10.fp18 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp6 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp6 |
| `com.liferay.portal:release.portal.bom` | Maven | All versions | 7.3.2 |
| `com.liferay.portal:release.portal.bom` | Maven | All versions | 7.3.2 |

Products: Liferay Liferay Portal.

## How do I fix CVE-2020-13445?

Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.0.10.fp92, 7.1.10.fp18 or 7.2.10.fp6.

## Is CVE-2020-13445 being exploited?

There is no known exploitation of CVE-2020-13445 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Liferay Portal

- [CVE-2020-7961](https://insights.sbomify.com/CVE-2020-7961/): Liferay Portal Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2021-33990](https://insights.sbomify.com/CVE-2021-33990/): File upload in n/a (critical 9.8)
- [CVE-2019-16891](https://insights.sbomify.com/CVE-2019-16891/): Liferay Portal Allows RCE via Deserialization of a JSON Payload (critical 9.8)
- [CVE-2023-47797](https://insights.sbomify.com/CVE-2023-47797/): Liferay Portal XSS with `p_l_back_url_title` on edit content page (critical 9.6)
- [CVE-2018-10795](https://insights.sbomify.com/CVE-2018-10795/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13445 and fix it if it is affected.

What it is: CVE-2020-13445 is a high-severity code injection vulnerability in Liferay Liferay Portal, published on 10 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-13445 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0; fixed in 7.0.10.fp92
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.0; fixed in 7.0.10.fp92
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp18
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0; fixed in 7.1.10.fp18
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp6
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp6
- com.liferay.portal:release.portal.bom (Maven): affected all versions; fixed in 7.3.2
- com.liferay.portal:release.portal.bom (Maven): affected all versions; fixed in 7.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-13445/ (Markdown: https://insights.sbomify.com/CVE-2020-13445/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13445
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13445
- OSV: https://osv.dev/vulnerability/CVE-2020-13445

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-13445/
Summaries are generated and may contain mistakes; the official description above is the record.
