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?

No patched version of com.liferay.portal:release.portal.bom has shipped for GHSA-c6g5-g6r7-q4j6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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)?

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.

How does O3 Security protect against GHSA-c6g5-g6r7-q4j6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c6g5-g6r7-q4j6 can be triaged on real exposure rather than presence alone.

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.2%, placing it in the 12th 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

GHSA-c6g5-g6r7-q4j6 — release.portal.bom

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.

Liferay Portal and Liferay DXP vulnerable to Server-Side Request Forgery

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 Sep 19, 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.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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`

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
No patched version of com.liferay.portal:release.portal.bom has shipped for GHSA-c6g5-g6r7-q4j6 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c6g5-g6r7-q4j6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-c6g5-g6r7-q4j6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

O3 Security finds GHSA-c6g5-g6r7-q4j6 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works