dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-4581

HIGH · 8.6 CVSS v3.1 Published 2025-08-09
Fix available
A fix is available. Upgrade to after 2025.q1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.4 ,2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.15, 7.4 GA through update 92 allows a pre-authentication blind SSRF vulnerability in the portal-settings-authentication-opensso-web due to improper validation of user-supplied URLs. An attacker can exploit this issue to force the server to make arbitrary HTTP requests to internal systems, potentially leading to internal network enumeration or further exploitation.

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

A pre-authentication blind SSRF vulnerability in L Portal/DXP's portal-settings-authentication-opensso-web module allows unauthenticated attackers to force the server to make arbitrary HTTP requests to internal systems due to improper validation of user-supplied URLs, enabling internal network enumeration and potential further exploitation.

MitigationUpgrade to L Portal 7.4.3.133+ or DXP versions beyond the affected ranges. If immediate patching is not feasible, disable the opensso-web module and implement network segmentation to restrict internal service exposure.

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.15>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.q1.0, <= 2025.q1.4= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, <= 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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/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 Liferav DXP version
    Determine the installed version of Liferav Digital Experience Platform. This is typically found in the product release notes, the control panel, or the portal properties file.
    Affected if The version falls within any of these ranges: 2024.q1.1 to 2024.q1.15, 2024.q2.0 to 2024.q2.13, 2024.q3.1 to 2024.q3.13, 2024.q4.0 to 2024.q4.7, 2025.q1.0 to 2025.q1.4, or equals 7.4
  2. Identify Liferav Portal version
    Determine the installed version of Liferav Portal. This is typically found in the product release notes, the control panel, or the portal properties file.
    Affected if The version is 7.4.0 through 7.4.3.132
  3. Check if opensso-web component is in use
    Inspect the portal configuration for the opensso-web authentication module. This is typically configured in the portal settings under authentication options or in the deployment descriptors.
    Affected if The opensso-web (OpenSSO) authentication component is enabled or configured in the environment

You are affected if you are running any Liferav DXP or Portal version within the affected ranges AND the opensso-web authentication component is enabled or configurable in your environment.

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 a release after 2025.q1.4
Interim mitigation

Upgrade to L Portal 7.4.3.133+ or DXP versions beyond the affected ranges. If immediate patching is not feasible, disable the opensso-web module and implement network segmentation to restrict internal service exposure.

Recommended fix High confidence

Liferary Portal: 7.4.3.133 or later / Liferary DXP (Digital Experience Platform): 2025.Q1.4 or later

  1. 1. Identify the exact Liferary product and version currently running (Portal or Digital Experience Platform)
  2. 2. For Liferary Portal users: Upgrade to version 7.4.3.133 or later (7.4.4+ recommended if available)
  3. 3. For Digital Experience Platform users: Upgrade to 2025.Q1.4 or later
  4. 4. After upgrade, verify the portal-settings-authentication-opensso-web module is updated and functioning correctly
  5. 5. Test that the SSRF vulnerability is remediated by confirming the OpenSSO authentication settings no longer accept arbitrary URLs without validation
Caveat Upgrading across major version branches (e.g., 7.4.x to 8.x) may require compatibility testing of custom plugins and themes; minor version upgrades within 7.4.x or 2024.x to 2025.x should have minimal breaking changes

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4581 — 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-4581 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