dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43760

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2024.Q4.7 / 2025.Q1.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 reflected cross-site scripting (XSS) vulnerability in the 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.6, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.20 and 7.4 GA through update 92 allows an remote authenticated attacker to inject JavaScript into the PortalUtil.escapeRedirect

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 · moderate confidence

Reflected XSS vulnerability in PortalUtil.escapeRedirect affects Liferay Portal 7.4.0-7.4.3.132 and DXP multiple quarterly versions (2025.Q1.0-Q1.4, 2024.Q4.0-Q4.6, 2024.Q3.0-Q3.13, 2024.Q2.0-Q2.13, 2024.Q1.1-Q1.20, 7.4 GA-92). An authenticated remote attacker can inject malicious JavaScript via unsanitized redirect parameters.

MitigationUpgrade to Liferays patched version or apply vendor fix to properly sanitize all input in PortalUtil.escapeRedirect to prevent script injection.

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.20>= 2024.q2.0, <= 2024.q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.Q4.0, < 2024.Q4.7>= 2025.Q1.0, < 2025.Q1.5= 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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. Locate installed Liferay version
    Check the Liferay control panel under Server > Server Information, or inspect the portal-ext.properties file, or look at the OSGi state at /o/osgi/state for bundle version information
    Affected if The version cannot be determined or is not visible in standard locations
  2. Compare Portal version to affected range
    Match your installed Liferay Portal version against 7.4.0 through 7.4.3.132. For DXP, match against: 2024.Q1.1-2024.Q1.20, 2024.Q2.0-2024.Q2.13, 2024.Q3.0-2024.Q3.13, 2024.Q4.0-2024.Q4.6, 2025.Q1.0-2025.Q1.4, or version 7.4 GA-92
    Affected if The installed version falls within any of the listed vulnerable version ranges
  3. Identify if escapeRedirect is in use
    Search deployed application code and custom portlets for calls to com.portal.util.PortalUtil.escapeRedirect method, or review redirect handling configurations that accept user-supplied URL parameters
    Affected if The escapeRedirect method is invoked with unsanitized redirect parameter input in your deployed modules or configurations

You are affected if your Liferay Portal or DXP version is within the specified ranges and the escapeRedirect method handles redirect parameters from user input.

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 2024.Q4.7 / 2025.Q1.5 or later
Fixed in 2024.Q4.72025.Q1.5
Interim mitigation

Upgrade to Liferays patched version or apply vendor fix to properly sanitize all input in PortalUtil.escapeRedirect to prevent script injection.

Recommended fix High confidence

Lixar Portal: 7.4.3.133+; DXP 2024.Q1: 2024.Q1.21+; DXP 2024.Q2: 2024.Q2.14+; DXP 2024.Q3: 2024.Q3.14+; DXP 2024.Q4: 2024.Q4.7+; DXP 2025.Q1: 2025.Q1.5+

  1. 1. Identify your current Lixar Portal or DXP version from the affected list (7.4.0-7.4.3.132 for Portal, or one of the DXP quarter releases 2024.Q1.x through 2024.Q4.x, or 2025.Q1.x)
  2. 2. For Lixar Portal 7.4.x: upgrade to version 7.4.3.133 or later which contains the fix for PortalUtil.escapeRedirect
  3. 3. For DXP 2024.Q1.x: upgrade to 2024.Q1.21 or later
  4. 4. For DXP 2024.Q2.x: upgrade to 2024.Q2.14 or later
  5. 5. For DXP 2024.Q3.x: upgrade to 2024.Q3.14 or later
  6. 6. For DXP 2024.Q4.x: upgrade to 2024.Q4.7 or later
  7. 7. For DXP 2025.Q1.x: upgrade to 2025.Q1.5 or later
  8. 8. After upgrade, verify the PortalUtil.escapeRedirect method properly escapes JavaScript in redirect URLs
Caveat Patch releases are typically backward compatible; review release notes for any deprecation notices

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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