How severe is GHSA-rpx3-f938-xj5q?

No CVSS score has been assigned to GHSA-rpx3-f938-xj5q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rpx3-f938-xj5q?

GHSA-rpx3-f938-xj5q affects the following packages: com.liferay:com.liferay.saml.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rpx3-f938-xj5q?

Update com.liferay:com.liferay.saml.impl to 5.0.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpx3-f938-xj5q is resolved across your whole dependency graph.

How do I detect GHSA-rpx3-f938-xj5q in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.saml.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-rpx3-f938-xj5q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rpx3-f938-xj5q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rpx3-f938-xj5q can be triaged on real exposure rather than presence alone.

Is GHSA-rpx3-f938-xj5q actively exploited in the wild?

No public exploit code has been indexed for GHSA-rpx3-f938-xj5q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rpx3-f938-xj5q?

GHSA-rpx3-f938-xj5q has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rpx3-f938-xj5q?

GHSA-rpx3-f938-xj5q is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rpx3-f938-xj5q published, and has it been updated?

GHSA-rpx3-f938-xj5q was published on September 24, 2025 and was last updated on December 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-rpx3-f938-xj5q — com.liferay.saml.impl

Fix: liferay/liferay-portal@433dff5

GHSA-rpx3-f938-xj5q is a CWE-613 vulnerability in com.liferay:com.liferay.saml.impl. A fix is available for com.liferay:com.liferay.saml.impl — see the affected versions and patch details below.

Liferay Portal and DXP does not properly expire sessions

Also known asCVE-2025-43819

Published

Sep 24, 2025

Updated

Dec 17, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rpx3-f938-xj5q.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.saml.impl

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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

Remediation

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.saml.impl`	all versions	5.0.51`com.liferay:com.liferay.saml.impl:5.0.51`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.saml.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.saml.impl to 5.0.51 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rpx3-f938-xj5q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rpx3-f938-xj5q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rpx3-f938-xj5q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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` ### Remediation Update to the fixed builds and, fo

O3 Security · Impact-Aware SCA

Is GHSA-rpx3-f938-xj5q in your dependencies?

O3 Security finds GHSA-rpx3-f938-xj5q across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works