# Liferay Portal Layout Module and Liferay DXP Exposes the Cross-Site Request Forgery (CSRF) Token in URLs

Advisory record · `GHSA-4frg-rpx6-96qh`

- **Identifiers:** `GHSA-4frg-rpx6-96qh` · `CVE-2021-33338`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 24 May 2022
- **Updated:** 28 May 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 May 2022, 19:10 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.1.0, <7.3.3`; fixed in `7.3.3`
- `com.liferay.portal:release.dxp.bom` (Maven): affected `>=7.1.0, <7.1.10.fp19 || >=7.2.0, <7.2.10.fp6`; fixed in `7.1.10.fp19`, `7.2.10.fp6`

## Machine-written summary

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

> Liferay Portal from 7.1.0 through 7.3.2 and Liferay DXP 7.1 before fix pack 19 and 7.2 before fix pack 6 expose the CSRF token in URLs through the Layout module. An attacker positioned as a man-in-the-middle can obtain the token and carry out cross-site request forgery attacks. Upgrade Liferay Portal to 7.3.3 or later, or Liferay DXP to 7.1.10 fix pack 19 or 7.2.10 fix pack 6 or later.

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0042, the 37th percentile, on 16 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-4frg-rpx6-96qh)

## Sources

- [GitHub Advisory Database: GHSA-4frg-rpx6-96qh](https://github.com/advisories/GHSA-4frg-rpx6-96qh)
- [OSV: GHSA-4frg-rpx6-96qh](https://osv.dev/vulnerability/GHSA-4frg-rpx6-96qh)
- <https://nvd.nist.gov/vuln/detail/CVE-2021-33338>
- <https://github.com/liferay/liferay-portal>
- <https://issues.liferay.com/browse/LPE-17030>
- <https://portal.liferay.dev/learn/security/known-vulnerabilities/-/asset_publisher/HbL5mxmVrnXW/content/id/120748276>

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-4frg-rpx6-96qh>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4frg-rpx6-96qh/>. Everything for agents: <https://agentprime.io/llms.txt>.
