Skip to content

← Public intelligence

Maven package

com.liferay:com.liferay.change.tracking.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

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

  1. Medium, CVSS 5.3MavenPublished

    Liferay Account Admin Web vulnerable to Authorization Bypass Through User-Controlled Key

    CVE-2025-62242 · GHSA-3cm9-jrf5-h2cx

    Affected
    • Maven com.liferay:com.liferay.change.tracking.web < 2.0.120
    Fixed in
    2.0.120· Vendor fix available
    Issue
    Insecure Direct Object Reference (IDOR) vulnerability with account addresses in Liferay Portal 7.4.3.4 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 allows remote authenticated users to from one account to view addresses from a different account via the comliferayaccountadminwebinternalportletAccountEntriesAdminPortletaddressId parameter.

    Recommended action: Upgrade to 2.0.120 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 4.8MavenPublished

    Liferay Publications vulnerable to Authorization Bypass Through User-Controlled Key

    CVE-2025-62244 · GHSA-2hfj-jv6q-762v

    Affected
    • Maven com.liferay:com.liferay.change.tracking.web < 2.0.122
    Fixed in
    2.0.122· Vendor fix available
    Issue
    Insecure direct object reference (IDOR) vulnerability in Publications in Liferay Portal 7.3.1 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92, and 7.3 GA through update 36 allows remote authenticated attackers to view the edit page of a publication via the comliferaychangetrackingwebportletPublicationsPortletctCollectionId parameter.

    Recommended action: Upgrade to 2.0.122 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 →
  3. Medium, CVSS 5.3MavenPublished

    Liferay Publications is vulnerable to Incorrect Authorization

    CVE-2025-62243 · GHSA-894w-w643-qvxv

    Affected
    • Maven com.liferay:com.liferay.change.tracking.web < 2.0.122
    Fixed in
    2.0.122· Vendor fix available
    Issue
    Insecure direct object reference (IDOR) vulnerability in Publications in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 allows remote authenticated attackers to view publication comments via the comliferaychangetrackingwebportletPublicationsPortletvalue parameter. Publications comments in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 GA through update 92 does not properly check user permissions, which allows remote authenticated users to edit publication comments via crafted URLs.

    Recommended action: Upgrade to 2.0.122 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 →
  4. Medium, CVSS 5.1MavenPublished

    Liferay Portal is vulnerable to CSRF through publication comments

    CVE-2025-62245 · GHSA-9676-rh83-cr86

    Affected
    • Maven com.liferay:com.liferay.change.tracking.web >= 2.0.9, < 2.0.121
    Fixed in
    2.0.121· Vendor fix available
    Issue
    Cross-site request forgery (CSRF) vulnerability in Liferay Portal 7.4.1 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows remote attackers to add and edit publication comments.

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