How severe is GHSA-894w-w643-qvxv?

No CVSS score has been assigned to GHSA-894w-w643-qvxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-894w-w643-qvxv?

GHSA-894w-w643-qvxv affects the following packages: com.liferay:com.liferay.change.tracking.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-894w-w643-qvxv?

Update com.liferay:com.liferay.change.tracking.web to 2.0.122 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-894w-w643-qvxv is resolved across your whole dependency graph.

How do I detect GHSA-894w-w643-qvxv in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.change.tracking.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-894w-w643-qvxv if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-894w-w643-qvxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-894w-w643-qvxv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-894w-w643-qvxv?

GHSA-894w-w643-qvxv has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-894w-w643-qvxv?

GHSA-894w-w643-qvxv is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-894w-w643-qvxv published, and has it been updated?

GHSA-894w-w643-qvxv was published on October 13, 2025 and was last updated on October 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

Liferay Publications is vulnerable to Incorrect AuthorizationGHSA-894w-w643-qvxv

Fix: liferay/liferay-portal@8190bb3

GHSA-894w-w643-qvxv is a CWE-863 vulnerability in com.liferay:com.liferay.change.tracking.web. A fix is available for com.liferay:com.liferay.change.tracking.web — see the affected versions and patch details below.

Also known asCVE-2025-62243

Published

Oct 13, 2025

Updated

Oct 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-894w-w643-qvxv.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.change.tracking.web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.change.tracking.web`	all versions	2.0.122`com.liferay:com.liferay.change.tracking.web:2.0.122`

Affected Products

2 products · 96 configurations

Application

digital experience platformliferay

≥ 2023.q4.0 && < 2023.q4.6

1 version

7.4

Application

liferay portalliferay

≥ 7.4.1 && < 7.4.3.113

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.change.tracking.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.change.tracking.web to 2.0.122 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-894w-w643-qvxv is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

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 `_com_liferay_change_tracking_web_portlet_PublicationsPortlet_value` 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 remot

O3 Security · Impact-Aware SCA

Is GHSA-894w-w643-qvxv in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works