How severe is GHSA-f5vh-4rj2-w8r8?

No CVSS score has been assigned to GHSA-f5vh-4rj2-w8r8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f5vh-4rj2-w8r8?

GHSA-f5vh-4rj2-w8r8 affects the following packages: com.liferay.portal:release.portal.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-f5vh-4rj2-w8r8?

Update com.liferay.portal:release.portal.bom to 7.4.3.110 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5vh-4rj2-w8r8 is resolved across your whole dependency graph.

How do I detect GHSA-f5vh-4rj2-w8r8 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-f5vh-4rj2-w8r8 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-f5vh-4rj2-w8r8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-f5vh-4rj2-w8r8 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-f5vh-4rj2-w8r8?

GHSA-f5vh-4rj2-w8r8 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th 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-f5vh-4rj2-w8r8?

GHSA-f5vh-4rj2-w8r8 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-f5vh-4rj2-w8r8 published, and has it been updated?

GHSA-f5vh-4rj2-w8r8 was published on October 30, 2025 and was last updated on October 31, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Liferay Portal is vulnerable to DNS rebinding attacks

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-f5vh-4rj2-w8r8.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% 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.portal:release.portal.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

By default, Liferay Portal 7.4.0 through 7.4.3.119, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions is vulnerable to DNS rebinding attacks, which allows remote attackers to redirect users to arbitrary external URLs. This vulnerability can be mitigated by changing the redirect URL security from IP to domain.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.0-ga1&&< 7.4.3.110	7.4.3.110`com.liferay.portal:release.portal.bom:7.4.3.110`

Affected Products

2 products · 142 configurations

Application

digital experience platformliferay

15 versions

7.37.42023.q3.12023.q3.22023.q3.32023.q3.42023.q3.52023.q3.62023.q3.72023.q4.02023.q4.12023.q4.2

Application

liferay portalliferay

≥ 7.4.0 && < 7.4.3.110

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
Update com.liferay.portal:release.portal.bom to 7.4.3.110 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f5vh-4rj2-w8r8 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Frequently Asked Questions

By default, Liferay Portal 7.4.0 through 7.4.3.119, and older unsupported versions, and Liferay DXP 2024.Q1.1 through 2024.Q1.5, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 GA through update 92, and older unsupported versions is vulnerable to DNS rebinding attacks, which allows remote attackers to redirect users to arbitrary external URLs. This vulnerability can be mitigated by changing the redirect URL security from IP to domain.

O3 Security · Impact-Aware SCA

Is GHSA-f5vh-4rj2-w8r8 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Liferay Portal is vulnerable to DNS rebinding attacksGHSA-f5vh-4rj2-w8r8