How severe is GHSA-2pwh-9q9q-5r9c?

No CVSS score has been assigned to GHSA-2pwh-9q9q-5r9c yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2pwh-9q9q-5r9c?

GHSA-2pwh-9q9q-5r9c affects the following packages: com.liferay:com.liferay.layout.admin.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2pwh-9q9q-5r9c?

Update com.liferay:com.liferay.layout.admin.web to 5.0.157 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pwh-9q9q-5r9c is resolved across your whole dependency graph.

How do I detect GHSA-2pwh-9q9q-5r9c in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.layout.admin.web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-2pwh-9q9q-5r9c 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-2pwh-9q9q-5r9c?

O3 pinpoints whether GHSA-2pwh-9q9q-5r9c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-2pwh-9q9q-5r9c actively exploited in the wild?

No public exploit code has been indexed for GHSA-2pwh-9q9q-5r9c 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 type of vulnerability is GHSA-2pwh-9q9q-5r9c?

GHSA-2pwh-9q9q-5r9c 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-2pwh-9q9q-5r9c published, and has it been updated?

GHSA-2pwh-9q9q-5r9c was published on October 27, 2025 and was last updated on October 29, 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-2pwh-9q9q-5r9c

Fix: liferay/liferay-portal@2835554

GHSA-2pwh-9q9q-5r9c is a Open Redirect vulnerability in com.liferay:com.liferay.layout.admin.web. O3 Security confirms whether GHSA-2pwh-9q9q-5r9c is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Liferay Portal Vulnerable to Open Redirect via the _com_liferay_layout_admin_web_portlet_GroupPagesPortlet_redirect parameter

Also known asCVE-2025-62253

Published

Oct 27, 2025

Updated

Oct 29, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.layout.admin.web

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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.layout.admin.web`	≥ 5.0.8&&< 5.0.157	5.0.157

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:com.liferay.layout.admin.web. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.liferay:com.liferay.layout.admin.web to 5.0.157 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2pwh-9q9q-5r9c is resolved across your whole dependency graph.
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 pinpoints whether GHSA-2pwh-9q9q-5r9c is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-2pwh-9q9q-5r9c. 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-2pwh-9q9q-5r9c in your dependencies?

O3 detects GHSA-2pwh-9q9q-5r9c across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works