# Liferay Portal and Liferay DXP Vulnerable to Cross-Site Scripting (XSS)

Advisory record · `GHSA-hrc4-p2h3-pjqw`

- **Identifiers:** `GHSA-hrc4-p2h3-pjqw` · `CVE-2025-2536`
- **State:** Confirmed
- **Severity:** CVSS 5.1 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-79](https://cwe.mitre.org/data/definitions/79.html)
- **Tags:** [Cross-site scripting (XSS)](https://agentprime.io/advisories/tag/xss.md)
- **Published:** 19 Mar 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 19 Mar 2025, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay.portal:release.dxp.bom` (Maven): affected `>=2024.Q2.0, <=2024.Q2.11 || >=2024.Q1.1, <2024.Q1.13 || >=2023.Q4.0, <2024.Q4.0 || >=2023.Q3.1, <2024.Q4.0 || >=2024.Q3.0, <2024.Q3.1`; fixed in `2024.Q1.13`, `2024.Q4.0`, `2024.Q3.1`
- `com.liferay.portal:release.portal.bom` (Maven): affected `>=7.4.3.82, <7.4.3.129`; fixed in `7.4.3.129`

## Machine-written summary

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

> Liferay Portal 7.4.3.82 through 7.4.3.128 and multiple Liferay DXP releases are affected by a cross-site scripting flaw in the Frontend JS module, where the toastData parameter can be used to inject arbitrary script or HTML. A remote attacker can exploit this to run script in a user's browser. Upgrade Liferay Portal to 7.4.3.129, or Liferay DXP to 2024.Q1.13, 2024.Q3.1, or 2024.Q4.0, depending on the release line in use. The source gives no workaround.

Written 2 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

- 5.1 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`, from CNA (Liferay)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0029, the 22nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:18 UTC: First seen by agentprime
- 31 Oct 2026, 14:18 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-hrc4-p2h3-pjqw)

## Sources

- [GitHub Advisory Database: GHSA-hrc4-p2h3-pjqw](https://github.com/advisories/GHSA-hrc4-p2h3-pjqw)
- [OSV: GHSA-hrc4-p2h3-pjqw](https://osv.dev/vulnerability/GHSA-hrc4-p2h3-pjqw)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-2536>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-2536>

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-hrc4-p2h3-pjqw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-hrc4-p2h3-pjqw/>. Everything for agents: <https://agentprime.io/llms.txt>.