How severe is GHSA-9676-rh83-cr86?

No CVSS score has been assigned to GHSA-9676-rh83-cr86 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9676-rh83-cr86?

GHSA-9676-rh83-cr86 affects the following packages: com.liferay:com.liferay.change.tracking.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-9676-rh83-cr86?

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

How do I detect GHSA-9676-rh83-cr86 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-9676-rh83-cr86 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-9676-rh83-cr86 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9676-rh83-cr86 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-9676-rh83-cr86?

GHSA-9676-rh83-cr86 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-9676-rh83-cr86?

GHSA-9676-rh83-cr86 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9676-rh83-cr86 published, and has it been updated?

GHSA-9676-rh83-cr86 was published on October 10, 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 Portal is vulnerable to CSRF through publication commentsGHSA-9676-rh83-cr86

Fix: liferay/liferay-portal@dd89fff

GHSA-9676-rh83-cr86 is a Cross-Site Request Forgery (CSRF) 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-62245

Published

Oct 10, 2025

Updated

Oct 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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-9676-rh83-cr86.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% 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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.change.tracking.web`	≥ 2.0.9&&< 2.0.121	2.0.121`com.liferay:com.liferay.change.tracking.web:2.0.121`

Affected Products

2 products · 4 configurations

Application

digital experience platformliferay

≥ 2023.q4.0 && ≤ 2023.Q3.10

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.121 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9676-rh83-cr86 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.