How severe is GHSA-c6g5-g6r7-q4j6?

No CVSS score has been assigned to GHSA-c6g5-g6r7-q4j6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-c6g5-g6r7-q4j6?

GHSA-c6g5-g6r7-q4j6 affects the following packages: com.liferay.portal:release.portal.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-c6g5-g6r7-q4j6?

A fix is available for GHSA-c6g5-g6r7-q4j6; check the affected-versions list above or the advisory for the patched release of com.liferay.portal:release.portal.bom, then make sure no transitive dependency still pins the vulnerable range.

How do I detect GHSA-c6g5-g6r7-q4j6 in my Maven dependencies?

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

How do I mitigate GHSA-c6g5-g6r7-q4j6 if there is no patch (or I can't update yet)?

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Is GHSA-c6g5-g6r7-q4j6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-c6g5-g6r7-q4j6 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-c6g5-g6r7-q4j6?

GHSA-c6g5-g6r7-q4j6 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 17th 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-c6g5-g6r7-q4j6?

GHSA-c6g5-g6r7-q4j6 is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c6g5-g6r7-q4j6 published, and has it been updated?

GHSA-c6g5-g6r7-q4j6 was published on August 9, 2025 and was last updated on August 12, 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 and Liferay DXP vulnerable to Server-Side Request ForgeryGHSA-c6g5-g6r7-q4j6

GHSA-c6g5-g6r7-q4j6 is a Server-Side Request Forgery (SSRF) vulnerability in com.liferay.portal:release.portal.bom. A fix is available for com.liferay.portal:release.portal.bom — see the affected versions and patch details below.

Also known asCVE-2025-4655

Published

Aug 9, 2025

Updated

Aug 12, 2025

Affected

7 pkgs

Patched

2 / 7

Exploits

None indexed

Exploitation data as of Nov 4, 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-c6g5-g6r7-q4j6.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs17th percentile — riskier than 17% of all scored CVEsHighest risk

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

Real-World Exposure

7 pkgs affected

☕com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom

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

An SSRF vulnerability in FreeMarker templates in 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 template editors to bypass access validations via crafted URLs.

Affected Packages

7 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.0	No fix
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2025.Q1.0&&< 2025.Q1.6	2025.Q1.6`com.liferay.portal:release.dxp.bom:2025.Q1.6`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q4.0	No fix
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q3.1	No fix
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q2.0	No fix
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q1.0&&< 2024.Q1.16	2024.Q1.16`com.liferay.portal:release.dxp.bom:2024.Q1.16`

Affected Products

2 products · 99 configurations

Application

digital experience platformliferay

≥ 2025.Q1.0 && ≤ 2024.q4.7

1 version

7.4

Application

liferay portalliferay

≥ 7.4.0 && ≤ 7.4.3.132

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.portal:release.portal.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for GHSA-c6g5-g6r7-q4j6; check the affected-versions list above or the advisory for the patched release of com.liferay.portal:release.portal.bom, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-c6g5-g6r7-q4j6 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works