CVE-2025-4581 — release.portal.bom
HIGHCVE-2025-4581 is a high-severity (CVSS 8.6) 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
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-4581.
EPSS Exploitation Probability
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
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.bomReal-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
Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.4, 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 allow a pre-authentication blind SSRF vulnerability in the portal-settings-authentication-opensso-web component due to improper validation of user-supplied URLs. An attacker can exploit this issue to force the server to make arbitrary HTTP requests to internal systems, potentially leading to internal network enumeration or further exploitation.
Affected Packages
| 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.5 | 2025.Q1.5com.liferay.portal:release.dxp.bom:2025.Q1.5 |
| ☕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.16com.liferay.portal:release.dxp.bom:2024.Q1.16 |
Affected Products
digital experience platformliferayliferay portalliferayDetection & mitigation playbook
Open-source dependencyDetect
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 CVE-2025-4581; 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
Is CVE-2025-4581 in your dependencies?
Find it across Maven, including transitive dependencies.