Liferay Portal and Liferay DXP's HtmlUtil.escapeRedirect Can Be Circumvented via Two Forward Slashes

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2024-25609: 0.36% estimated exploitation activity in the next 30 days; percentile 29.24 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

HtmlUtil.escapeRedirect in Liferay Portal 7.2.0 through 7.4.3.12, and older unsupported versions, and Liferay DXP 7.4 before update 9, 7.3 service pack 3, 7.2 fix pack 15 through 18, and older unsupported versions can be circumvented by using two forward slashes, which allows remote attackers to redirect users to arbitrary external URLs via the (1) 'redirect parameter (2) FORWARDURL parameter, and (3) others parameters that rely on HtmlUtil.escapeRedirect. This vulnerability is the result of an incomplete fix in CVE-2022-28977.

Published by the source

20 Feb 2024, 12:31 UTC

Last modified by the source

15 Mar 2026, 05:07 UTC

Source last checked

26 Oct 2026, 16:44 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3qq5-wcrx-4h8r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25609

Advisory: Liferay Portal and Liferay DXP's HtmlUtil.escapeRedirect Can Be Circumvented via Two Forward Slashes
IDs: CVE-2024-25609, GHSA-3qq5-wcrx-4h8r
Record: https://patchnext.com/advisories/cve-2024-25609 (revision 1, source checked 26 Oct 2026, 16:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: com.liferay.portal:release.portal.bom 7.4.3.13-ga13; com.liferay.portal:release.dxp.bom 7.4.13.u9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.portal.bom: affected >= 7.2.0, < 7.4.3.13-ga13; fixed in 7.4.3.13-ga13
- Maven com.liferay.portal:release.dxp.bom: affected >= 7.2.10.fp15, <= 7.2.10.fp18; >= 7.4.0, < 7.4.13.u9; fixed in 7.4.13.u9

## Suggested inspection (read-only)
- Maven com.liferay.portal:release.portal.bom: check the installed version with your package manager.
- Maven com.liferay.portal:release.dxp.bom: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.portal.bom, com.liferay.portal:release.dxp.bom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3qq5-wcrx-4h8r (GitHub-reviewed advisory GHSA-3qq5-wcrx-4h8r lists affected ranges: Maven com.liferay.portal:release.portal.bom >=7.2.0 =7.2.10.fp15 =7.4.0 <7.4.13.u9)

Commands are suggestions: review each one before running it.