# Liferay Portal and DXP does not properly expire sessions

Advisory record · `GHSA-rpx3-f938-xj5q`

- **Identifiers:** `GHSA-rpx3-f938-xj5q` · `CVE-2025-43819`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-613](https://cwe.mitre.org/data/definitions/613.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 24 Sept 2025
- **Updated:** 17 Dec 2025
- **Reviewed by a person:** No

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

## Affected packages

- `com.liferay:com.liferay.saml.impl` (Maven): affected `<5.0.51`; fixed in `5.0.51`

## Machine-written summary

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

> Liferay Portal and DXP versions listed in the source, along with the Maven package com.liferay:com.liferay.saml.impl before 5.0.51, fail to properly invalidate a user's previous session through the Single Logout (SLO) API. An attacker can reuse a stale session via that endpoint to gain an authenticated context. Upgrade com.liferay.saml.impl to 5.0.51 or later, or update Liferay Portal or DXP to a fixed build.

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

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

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

## Timeline

- 31 Oct 2026, 15:09 UTC: First seen by agentprime
- 31 Oct 2026, 15:09 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-rpx3-f938-xj5q)

## Sources

- [GitHub Advisory Database: GHSA-rpx3-f938-xj5q](https://github.com/advisories/GHSA-rpx3-f938-xj5q)
- [OSV: GHSA-rpx3-f938-xj5q](https://osv.dev/vulnerability/GHSA-rpx3-f938-xj5q)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-43819>
- <https://github.com/liferay/liferay-portal/commit/433dff5edae4414fdc436b49a9edb62d721c84b5>
- <https://github.com/liferay/liferay-portal/commit/da9105a61d788801797797a32583a4b76c902cdc>
- <https://github.com/liferay/liferay-portal>
- <https://liferay.atlassian.net/browse/LPE-18159>
- <https://liferay.dev/portal/security/known-vulnerabilities/-/asset_publisher/jekt/content/CVE-2025-43819>
- <https://osv.dev/vulnerability/GHSA-rpx3-f938-xj5q>

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

---

The web page: <https://agentprime.io/advisories/GHSA-rpx3-f938-xj5q/>. Everything for agents: <https://agentprime.io/llms.txt>.