Skip to content

← Public intelligence

Maven package

com.liferay:com.liferay.layout.taglib

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 2.1MavenPublished

    Liferay Portal Reflected Cross-Site Scripting Vulnerability via Form Container

    CVE-2025-43753 · GHSA-r367-q549-pgr5

    Affected
    • Maven com.liferay:com.liferay.layout.taglib < 16.1.32
    Fixed in
    16.1.32· Vendor fix available
    Issue
    A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.3.32 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.16 and 7.4 update 32 through update 92 allows an remote authenticated user to inject JavaScript into the embedded message field from the form container.

    Recommended action: Upgrade to 16.1.32 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Low, CVSS 2.3MavenPublished

    Liferay Portal Vulnerable to Cross-Site Scripting

    CVE-2025-43733 · GHSA-vhcr-hgc8-29qr

    Affected
    • Maven com.liferay:com.liferay.layout.taglib < 17.0.0
    Fixed in
    17.0.0· Vendor fix available
    Issue
    A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.7 allows a remote authenticated attacker to inject JavaScript code via the content page's name field. This malicious payload is then reflected and executed within the user's browser when viewing the "document View Usages" page. Liferay Portal is fixed on the master branch from commit 2135a88.

    Recommended action: Upgrade to 17.0.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →