# Liferay Portal's Membership page is vulnerable to XSS through “name“ text field

Advisory record · `GHSA-xw6m-3m5q-mxpm`

- **Identifiers:** `GHSA-xw6m-3m5q-mxpm` · `CVE-2025-62238`
- **State:** Confirmed
- **Severity:** CVSS 4.8 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:** 10 Oct 2025
- **Updated:** 11 Oct 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Oct 2025, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.liferay:com.liferay.account.admin.web` (Maven): affected `>=2.0.40, <2.0.114`; fixed in `2.0.114`

## Machine-written summary

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

> Liferay's com.liferay.account.admin.web package, versions 2.0.40 up to 2.0.114, contains a stored cross-site scripting flaw on the Membership page in Account Settings, where the Account "Name" text field is not properly sanitized. An authenticated attacker can inject a crafted payload into that field, which runs arbitrary script or HTML in the browsers of users who view the page. Upgrade to version 2.0.114, which fixes the issue.

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

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

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

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xw6m-3m5q-mxpm)

## Sources

- [GitHub Advisory Database: GHSA-xw6m-3m5q-mxpm](https://github.com/advisories/GHSA-xw6m-3m5q-mxpm)
- [OSV: GHSA-xw6m-3m5q-mxpm](https://osv.dev/vulnerability/GHSA-xw6m-3m5q-mxpm)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-62238>
- <https://github.com/liferay/liferay-portal/commit/89a043bface29bf924e25d1c2c3b05f85d750a75>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.atlassian.net/browse/LPE-17920>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-62238>

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-xw6m-3m5q-mxpm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xw6m-3m5q-mxpm/>. Everything for agents: <https://agentprime.io/llms.txt>.