Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

com.liferay:com.liferay.frontend.js.web

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. Medium, CVSS 5.3MavenPublished

    Liferay Portal's unauthenticated users can access loaded files via URL before submitting the object entry

    CVE-2025-43758 · GHSA-mm62-gwj5-j285

    Affected
    • Maven com.liferay:com.liferay.frontend.js.web < 5.0.125
    Fixed in
    5.0.125· Vendor fix available
    Issue
    Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.5, 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 and 7.4 GA through update 92 allows unauthenticated users (guests) to access via URL files uploaded by object entry and stored in documentlibrary

    Recommended action: Upgrade to 5.0.125 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. Medium, CVSS 5.4MavenPublished

    Liferay Portal and Liferay DXP vulnerable to cross-site scripting (XSS) in edit blog entry page

    CVE-2021-38267 · GHSA-r39x-3qq4-gxmr

    Affected
    • Maven com.liferay:com.liferay.frontend.js.web < 5.0.0
    Fixed in
    5.0.0· Vendor fix available
    Issue
    Cross-site scripting (XSS) vulnerability in the Blogs module's edit blog entry page in Liferay Portal 7.3.2 through 7.3.6, and Liferay DXP 7.3 before fix pack 2 allows remote attackers to inject arbitrary web script or HTML via the comliferayblogswebportletBlogsAdminPortlettitle and comliferayblogswebportletBlogsAdminPortletsubtitle parameter.

    Recommended action: Upgrade to 5.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 →