# CVE-2025-62253: Liferay Portal Vulnerable to Open Redirect via the _com_liferay_layout_admin_web_portlet_GroupPagesPortlet_redirect parameter

> Remote attackers can redirect users to arbitrary external URLs via a specific parameter in Liferay Portal page administration.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-2pwh-9q9q-5r9c

## What is CVE-2025-62253?

CVE-2025-62253 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open redirect vulnerability in page administration in Liferay Portal 7.4.0 through 7.4.3.97, and older unsupported versions, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to redirect users to arbitrary external URLs via the _com_liferay_layout_admin_web_portlet_GroupPagesPortlet_redirect parameter.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2025-62253?

2 open source packages ship an affected version, including com.liferay:com.liferay.layout.admin.web. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay:com.liferay.layout.admin.web` | Maven | From 5.0.8 | 5.0.157 |
| `com.liferay:com.liferay.layout.admin.web` | Maven | From 5.0.8 | 5.0.157 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2025-62253?

Upgrade com.liferay:com.liferay.layout.admin.web to 5.0.157 or later.

## Is CVE-2025-62253 being exploited?

There is no known exploitation of CVE-2025-62253 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Digital Experience Platform

- [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6)
- [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)
- [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62253 and fix it if it is affected.

What it is: CVE-2025-62253 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 27 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62253 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay:com.liferay.layout.admin.web (Maven): affected from 5.0.8; fixed in 5.0.157
- com.liferay:com.liferay.layout.admin.web (Maven): affected from 5.0.8; fixed in 5.0.157

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62253/ (Markdown: https://insights.sbomify.com/CVE-2025-62253/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62253
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62253
- OSV: https://osv.dev/vulnerability/CVE-2025-62253

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62253/
Summaries are generated and may contain mistakes; the official description above is the record.