dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-2536

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to after 2024.q2.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting (XSS) vulnerability on Liferay Portal 7.4.3.82 through 7.4.3.128, and Liferay DXP 2024.Q3.0, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 update 82 through update 92 in the Frontend JS module's layout-taglib/__liferay__/index.js allows remote attackers to inject arbitrary web script or HTML via toastData parameter

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

Cross-site scripting (XSS) vulnerability in Liferay Portal and DXP's Frontend JS module (layout-taglib/__lifera__/index.js) allows injection of arbitrary web script or HTML via the toastData parameter. The vulnerability is exploitable remotely with user interaction (likely clicking a crafted link).

MitigationUpgrade to a patched Liferay version beyond 7.4.3.128/2024.Q3.0, or implement server-side input validation and output encoding on the toastData parameter before rendering. Consider adding Content-Security-Policy headers to mitigate XSS impact.

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:>= 2023.Q3.1, <= 2023.Q3.10>= 2023.q4.0, <= 2023.q4.10>= 2024.q1.1, <= 2024.q1.12>= 2024.q2.0, <= 2024.q2.13= 7.4= 2024.q3.0
Liferay PortalApplication
Affected:>= 7.4.3.82, <= 7.4.3.128

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify the installed Liferay version
    Check the Liferay bundle or WAR file for the version manifest. In a Liferay Tomcat bundle, this is typically in liferay-portal-tomcat-*/WEB-INF/lib/portal-impl.jar under com/liferay/portal/util/Build.properties, or check the system-level bundle info via the Liferay Control Panel under Configuration > Server Administration > Build Information. Alternatively, examine the portal-release.properties file in the portal-impl.jar.
    Affected if The installed version falls within the affected ranges: Liferay DXP 2023.Q3.1 through 2023.Q3.10, 2023.q4.0 through 2023.q4.10, 2024.q1.1 through 2024.q1.12, 2024.q2.0 through 2024.q2.13, 7.4, or 2024.q3.0; or Liferay Portal 7.4.3.82 through 7.4.3.128.
  2. Confirm the layout-taglib module is deployed
    Locate the layout-taglib module in the deployed web application. In a Liferay bundle, search for the __lifera__ path under the deployed portal webapp, typically in webapps/ROOT/html/taglib/ui/layout/__lifera__/ or verify the presence of index.js at that path within the deployed WAR file.
    Affected if The layout-taglib/__lifera__/index.js file exists in the deployed application.
  3. Verify the vulnerable toastData parameter acceptance
    Inspect the index.js file located at layout-taglib/__lifera__/index.js in the deployed webapp. Search for code handling a toastData parameter, particularly any client-side rendering or DOM insertion logic that processes this parameter without server-side sanitization.
    Affected if The index.js file accepts and processes a toastData parameter via client-side rendering without documented server-side input validation.
  4. Check if the endpoint is network-accessible
    Determine whether the affected endpoint at /layout-taglib/__lifera__/ is accessible from the network. Review the web server configuration and firewall rules to confirm whether unauthenticated or authenticated users can reach this path.
    Affected if The /layout-taglib/__lifera__/ endpoint is accessible to users who could be tricked into clicking a malicious link.

A Liferay installation is affected if it runs a version within the specified ranges AND has the layout-taglib/__lifera__/index.js module deployed with the vulnerable toastData parameter handling accessible to users.

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 2024.q2.13
Interim mitigation

Upgrade to a patched Liferay version beyond 7.4.3.128/2024.Q3.0, or implement server-side input validation and output encoding on the toastData parameter before rendering. Consider adding Content-Security-Policy headers to mitigate XSS impact.

Recommended fix Moderate confidence

Lifteray Portal: upgrade to 7.4.3.129 or later; Liferay DXP: upgrade to first release beyond each affected quarter (2023.Q3.11, 2023.Q4.11, 2024.Q1.13, 2024.Q2.14, 2024.Q3.1)

  1. 1. Identify the exact currently-deployed Lifteray version (Portal or DXP) from the Liferay Control Panel > Configuration > Server Administration > Build information
  2. 2. For Liferay Portal 7.4.x: upgrade to version 7.4.3.129 or later (which contains the fix beyond update 92)
  3. 3. For Liferay DXP 2023.Q3.x: upgrade to 2023.Q3.11 or later
  4. 4. For Liferay DXP 2023.Q4.x: upgrade to 2023.Q4.11 or later
  5. 5. For Liferay DXP 2024.Q1.x: upgrade to 2024.Q1.13 or later
  6. 6. For Liferay DXP 2024.Q2.x: upgrade to 2024.Q2.14 or later
  7. 7. For Liferay DXP 2024.Q3.x: upgrade to 2024.Q3.1 or later
  8. 8. After upgrade, verify the layout-taglib module has been updated and confirm toastData parameter is now properly sanitized
Caveat Standard Liferay upgrade precautions apply: backup data, test in staging environment, review breaking changes in release notes, ensure custom plugins are compatible with the target version

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-2536 — 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-2536 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