How severe is CVE-2025-62243?

CVE-2025-62243 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-62243?

CVE-2025-62243 affects the following packages: com.liferay:com.liferay.change.tracking.web (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-62243?

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 CVE-2025-62243 is resolved across your whole dependency graph.

How do I detect CVE-2025-62243 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 CVE-2025-62243 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 CVE-2025-62243 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-62243 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 CVE-2025-62243?

CVE-2025-62243 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 CVE-2025-62243?

CVE-2025-62243 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 CVE-2025-62243 published, and has it been updated?

CVE-2025-62243 was published on October 13, 2025 and was last updated on October 24, 2026. 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

MEDIUM severity

CVE-2025-62243 — com.liferay.change.tracki…

MEDIUMFix: liferay/liferay-portal@8190bb3

CVE-2025-62243 is a medium-severity (CVSS 5.4) 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.

Liferay Publications is vulnerable to Incorrect Authorization

Also known asGHSA-894w-w643-qvxv

Published

Oct 13, 2025

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 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 CVE-2025-62243.

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.

How urgent is this, really

Where this sits among everything scored

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 CVE-2025-62243 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 remote

O3 Security · Impact-Aware SCA

Is CVE-2025-62243 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

liferay-portal

2.5/10

Code-Review0/10

Maintained10/10

Branch-Protection0/10

Assessed Nov 2, 2026

Timeline

Disclosed

Oct 13, 2025

Last updated

Oct 24, 2026

Identifiers

CVE-2025-62243

GHSA-894w-w643-qvxv

References

Advisoryliferay.dev · CVE 2025 62243 Advisorynvd.nist.gov · CVE 2025 62243 Webgithub.com · 8190bb30e8a111879d92e256bded575857696c5a Webgithub.com · e1457adf84fd596c6ec5a982adef97d7962347a4 Webgithub.com · f68ecf7fd8e08aba5fb806eb61d2c0f8ec6adec8 Packagegithub.com · liferay portal

Related vulnerabilities

Also affects com.liferay.change.tracking.web

This CVE is medium severity, in line with the other 3 CVEs affecting com.liferay.change.tracking.web.

CVE-2025-62244CVE-2025-62242CVE-2025-62245

Same weakness: CWE-863

This CVE is medium severity; 5 of 5 other CVEs with CWE-863 are rated as high or higher (top: high).

CVE-2026-55098GHSA-j656-3hf2-fvjcCVE-2026-118669CVE-2026-119200GHSA-fgxm-5hvv-x4vhBrowse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026