Summary
Liferay Portal and Liferay DXP vulnerable to Server-Side Request Forgery
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.
Impact
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
com.liferay.portal:release.dxp.bom to 2025.Q1.6 or later; com.liferay.portal:release.dxp.bom to 2024.Q1.16 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-4655? CVE-2025-4655 is a medium-severity server-side request forgery (SSRF) vulnerability in com.liferay.portal:release.portal.bom (maven), affecting versions >= 7.4.0, <= 7.4.3.132. It is fixed in 2025.Q1.6, 2024.Q1.16. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
- Which packages are affected by CVE-2025-4655?
com.liferay.portal:release.portal.bom(maven) (versions >= 7.4.0, <= 7.4.3.132)com.liferay.portal:release.dxp.bom(maven) (versions >= 2025.Q1.0, <= 2025.Q1.5)
- Is there a fix for CVE-2025-4655? Yes. CVE-2025-4655 is fixed in 2025.Q1.6, 2024.Q1.16. Upgrade to this version or later.
- Is CVE-2025-4655 exploitable, and should I be worried? Whether CVE-2025-4655 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-4655 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-4655?
- Upgrade
com.liferay.portal:release.dxp.bomto 2025.Q1.6 or later - Upgrade
com.liferay.portal:release.dxp.bomto 2024.Q1.16 or later
- Upgrade