# CVE-2023-47798: Liferay Portal's account lockout does not invalidate existing user sessions

> Authenticated users can maintain active sessions after account lockout, bypassing security controls in Liferay Portal and DXP.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Feb 2024
- **Updated:** 15 May 2025
- **Also known as:** GHSA-2mx7-xvfg-fg53

## What is CVE-2023-47798?

CVE-2023-47798 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Account lockout in Liferay Portal 7.2.0 through 7.3.0, and older unsupported versions, and Liferay DXP 7.2 before fix pack 5, and older unsupported versions does not invalidate existing user sessions, which allows remote authenticated users to remain authenticated after an account has been locked.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2023-47798?

4 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp5 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp5 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.3.1 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.2.0 | 7.3.1 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2023-47798?

Upgrade com.liferay.portal:release.dxp.bom to 7.2.10.fp5 or later.

## Is CVE-2023-47798 being exploited?

There is no known exploitation of CVE-2023-47798 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Digital Experience Platform

- [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6)
- [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)
- [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47798 and fix it if it is affected.

What it is: CVE-2023-47798 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 8 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-47798 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp5
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp5
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.3.1
- com.liferay.portal:release.portal.bom (Maven): affected from 7.2.0; fixed in 7.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-47798/ (Markdown: https://insights.sbomify.com/CVE-2023-47798/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47798
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47798
- OSV: https://osv.dev/vulnerability/CVE-2023-47798

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47798/
Summaries are generated and may contain mistakes; the official description above is the record.