dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43819

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 7.4.3.132 / 2024.Q1.13 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Insufficient Session Expiration vulnerability in the Liferay Portal 7.4.3.121 through 7.3.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.3, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, and 2024.Q1.1 through 2024.Q1.12 is allow an remote non-authenticated attacker to reuse old user session by SLO API

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Lifter DXP and Portal versions 7.3-7.4 and 2024.Q1-Q4 contain an Insufficient Session Expiration vulnerability in the SLO (Single Logout) API. Remote unauthenticated attackers can reuse old user sessions after logout because sessions are not properly invalidated, allowing session hijacking of previously authenticated users.

MitigationApply vendor-provided patches for the affected versions or upgrade to a patched Lifier DXP/Portal release. Verify session invalidation behavior after implementing the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digital Experience PlatformApplication
Affected:>= 2024.Q1.1, < 2024.Q1.13>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.Q4.0, < 2024.Q4.4= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.121, < 7.4.3.132

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lifer DXP or Portal version
    Locate the version file or check the portal administration interface for the installed Lifer version. Check files such as version.properties, portal-impl.properties, or the Server Info page in the control panel.
    Affected if The installed version falls within any of these ranges: >= 2024.Q1.1 and < 2024.Q1.13; >= 2024.q2.0 and <= 2024.q2.13; >= 2024.q3.1 and <= 2024.q3.13; >= 2024.Q4.0 and < 2024.Q4.4; version 7.4; or >= 7.4.3.121 and < 7.4.3.132 (for Lifer Portal).
  2. Verify SLO module availability
    Check the Lifer module registry or bundle list for the SLO (Single Logout) related modules. Look for com_lifer_slo or similar SLO bundle names in the OSGi console or through the Lifer Bundle Viewer.
    Affected if The SLO module is installed and active in the Lifer environment.
  3. Confirm SLO configuration is enabled
    Review portal-ext.properties, portal.properties, or the SAML/SSO configuration in the Lifer control panel for single logout settings. Look for properties such as sso.slo.enabled=true or related SLO configuration entries.
    Affected if Single Logout is explicitly enabled in the Lifer configuration.
  4. Test session invalidation behavior
    Authenticate to the Lifer portal, initiate a logout, then attempt to replay the original session cookie or token. Use browser developer tools or a tool like curl to replay the session identifier after logout.
    Affected if The original session remains valid and accessible after logout, indicating sessions are not properly invalidated.

A user is affected if they run a Lifer DXP/Portal version within the affected ranges AND have SLO enabled, as the session will not be invalidated properly after logout.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.3.132 / 2024.Q1.13 / 2024.Q4.4 or later
Fixed in 7.4.3.1322024.Q1.132024.Q4.4
Interim mitigation

Apply vendor-provided patches for the affected versions or upgrade to a patched Lifier DXP/Portal release. Verify session invalidation behavior after implementing the update.

Recommended fix High confidence

Lifera Portal 7.4.3.132 or DXP 2024.Q1.13/2024.Q2.13/2024.Q3.13/2024.Q4.4 depending on release train

  1. 1. Identify the current Lifeswitcher/DXP version by checking the portal's version information
  2. 2. For Liferay Portal 7.4.3.x users: upgrade to version 7.4.3.132 or later
  3. 3. For DXP 2024.Q1.x users: upgrade to version 2024.Q1.13 or later
  4. 4. For DXP 2024.Q2.x users: upgrade to version 2024.Q2.13 or later
  5. 5. For DXP 2024.Q3.x users: upgrade to version 2024.Q3.13 or later
  6. 6. For DXP 2024.Q4.x users: upgrade to version 2024.Q4.4 or later
  7. 7. After upgrade, verify the session expiration configuration in portal-ext.properties or via the control panel under Session Management
  8. 8. Test the SLO (Single Log-Out) functionality to confirm the fix is working properly
Caveat Security patch release with minimal breaking changes expected; always review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43819 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data