# Liferay Portal and Liferay DXP have Insecure Deserialization Vulnerability

Advisory record · `GHSA-mg3r-9jh8-33r9`

- **Identifiers:** `GHSA-mg3r-9jh8-33r9` · `CVE-2020-15842`
- **State:** Confirmed
- **Severity:** CVSS 8.1 High
- **Critical:** No
- **Weakness (CWE):** [CWE-502](https://cwe.mitre.org/data/definitions/502.html)
- **Tags:** [Insecure deserialization](https://agentprime.io/advisories/tag/deserialization.md)
- **Published:** 24 May 2022
- **Updated:** 28 May 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 17:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay.portal:release.portal.bom` (Maven): affected `<7.3.0`; fixed in `7.3.0`
- `com.liferay.portal:release.dxp.bom` (Maven): affected `>=7.0.0, <7.0.10.fp90 || >=7.1.0, <7.1.10.fp17 || >=7.2.0, <7.2.10.fp5`; fixed in `7.0.10.fp90`, `7.1.10.fp17`, `7.2.10.fp5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Liferay Portal before 7.3.0 and Liferay DXP 7.0 before fix pack 90, 7.1 before fix pack 17, and 7.2 before fix pack 5 are affected. A man-in-the-middle attacker can send crafted serialized data that is insecurely deserialized, allowing arbitrary code execution. Upgrade Liferay Portal to 7.3.0 or Liferay DXP to 7.0.10.fp90, 7.1.10.fp17, or 7.2.10.fp5.

Written 7 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.1 High, CVSS 3.1: `CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`, from CNA (mitre)

- **CISA KEV:** Not listed.
- **EPSS:** 0.018, the 78th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:11 UTC: First seen by agentprime
- 31 Oct 2026, 15:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mg3r-9jh8-33r9)

## Sources

- [GitHub Advisory Database: GHSA-mg3r-9jh8-33r9](https://github.com/advisories/GHSA-mg3r-9jh8-33r9)
- [OSV: GHSA-mg3r-9jh8-33r9](https://osv.dev/vulnerability/GHSA-mg3r-9jh8-33r9)
- <https://nvd.nist.gov/vuln/detail/CVE-2020-15842>
- <https://github.com/liferay/liferay-portal>
- <https://issues.liferay.com/browse/LPE-16963>
- <https://portal.liferay.dev/learn/security/known-vulnerabilities/-/asset_publisher/HbL5mxmVrnXW/content/id/119317427>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-mg3r-9jh8-33r9>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mg3r-9jh8-33r9/>. Everything for agents: <https://agentprime.io/llms.txt>.
