What is CVE-2025-43819?

CVE-2025-43819 is a medium-severity security vulnerability in com.liferay:com.liferay.saml.impl (maven), affecting versions < 5.0.51. It is fixed in 5.0.51.

Which versions of com.liferay:com.liferay.saml.impl are affected by CVE-2025-43819?

com.liferay:com.liferay.saml.impl (maven) versions < 5.0.51 is affected.

Is there a fix for CVE-2025-43819?

Yes. CVE-2025-43819 is fixed in 5.0.51. Upgrade to this version or later.

Is CVE-2025-43819 exploitable, and should I be worried?

Whether CVE-2025-43819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-43819 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-43819 in com.liferay:com.liferay.saml.impl

Q: Which versions of com.liferay:com.liferay.saml.impl are affected by CVE-2025-43819?

com.liferay:com.liferay.saml.impl (maven) versions < 5.0.51 is affected.

Q: Is there a fix for CVE-2025-43819?

Yes. CVE-2025-43819 is fixed in 5.0.51. Upgrade to this version or later.

Q: Is CVE-2025-43819 exploitable, and should I be worried?

Whether CVE-2025-43819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-43819 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-43819?

Upgrade com.liferay:com.liferay.saml.impl to 5.0.51 or later.

Summary

Liferay Portal and DXP does not properly expire sessions

Liferay Portal/DXP contains an Insufficient Session Expiration issue where the Single Logout (SLO) API may fail to invalidate a user’s previous session. An attacker can reuse a stale session via the SLO endpoint to gain an authenticated context.

Affected Versions

The following platform versions are affected:

Liferay Portal:
- 7.3.3.131 through 7.4.3.121
Liferay DXP:
- 2024.Q4.0–2024.Q4.3
- 2024.Q3.1–2024.Q3.13
- 2024.Q2.0–2024.Q2.13
- 2024.Q1.1–2024.Q1.12

Impact

Affected versions

com.liferay:com.liferay.saml.impl (< 5.0.51)

Security releases

com.liferay:com.liferay.saml.impl → 5.0.51 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Update to the fixed builds and, for Maven consumers of the SAML module, upgrade com.liferay:com.liferay.saml.impl to 5.0.51 or later. After upgrading, ensure session invalidation policies are enforced and verify SLO behavior end-to-end.

Frequently Asked Questions

What is CVE-2025-43819? CVE-2025-43819 is a medium-severity security vulnerability in com.liferay:com.liferay.saml.impl (maven), affecting versions < 5.0.51. It is fixed in 5.0.51.
Which versions of com.liferay:com.liferay.saml.impl are affected by CVE-2025-43819? com.liferay:com.liferay.saml.impl (maven) versions < 5.0.51 is affected.
Is there a fix for CVE-2025-43819? Yes. CVE-2025-43819 is fixed in 5.0.51. Upgrade to this version or later.
Is CVE-2025-43819 exploitable, and should I be worried? Whether CVE-2025-43819 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-43819 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-43819? Upgrade com.liferay:com.liferay.saml.impl to 5.0.51 or later.