# Liferay Portal's account lockout does not invalidate existing user sessions

Advisory record · `GHSA-2mx7-xvfg-fg53`

- **Identifiers:** `GHSA-2mx7-xvfg-fg53` · `CVE-2023-47798`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-384](https://cwe.mitre.org/data/definitions/384.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 8 Feb 2024
- **Updated:** 3 Oct 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 8 Feb 2024, 03:32 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.2.0, <7.3.1`; fixed in `7.3.1`
- `com.liferay.portal:release.dxp.bom` (Maven): affected `>=7.2.0, <7.2.10.fp5`; fixed in `7.2.10.fp5`

## Machine-written summary

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

> Liferay Portal 7.2.0 through 7.3.0 and Liferay DXP 7.2 before fix pack 5 (7.2.10.fp5) do not invalidate existing user sessions when an account is locked out. A remote authenticated user can therefore stay signed in after their account has been locked. Upgrade Liferay Portal to 7.3.1 or Liferay DXP to 7.2.10.fp5.

Written 8 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.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`, from CNA (Liferay)

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

## Timeline

- 31 Oct 2026, 15:13 UTC: First seen by agentprime
- 31 Oct 2026, 15:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-2mx7-xvfg-fg53)

## Sources

- [GitHub Advisory Database: GHSA-2mx7-xvfg-fg53](https://github.com/advisories/GHSA-2mx7-xvfg-fg53)
- [OSV: GHSA-2mx7-xvfg-fg53](https://osv.dev/vulnerability/GHSA-2mx7-xvfg-fg53)
- <https://nvd.nist.gov/vuln/detail/CVE-2023-47798>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/cve-2023-47798>

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-2mx7-xvfg-fg53>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-2mx7-xvfg-fg53/>. Everything for agents: <https://agentprime.io/llms.txt>.