Open Redirect in Liferay Portal

Exploitation

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

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2020-24554: 1.76% estimated exploitation activity in the next 30 days; percentile 78.00 (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.

The redirect module in Liferay Portal before 7.3.3 does not limit the number of URLs resulting in a 404 error that is recorded, which allows remote attackers to perform a denial of service attack by making repeated requests for pages that do not exist.

Published by the source

7 May 2021, 15:54 UTC

Last modified by the source

1 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:06 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mg53-xr8m-86hw

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

# Patch Next advisory brief: CVE-2020-24554

Advisory: Open Redirect in Liferay Portal
IDs: CVE-2020-24554, GHSA-mg53-xr8m-86hw
Record: https://patchnext.com/advisories/cve-2020-24554 (revision 1, source checked 26 Oct 2026, 16:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay.portal:release.portal.bom 7.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.portal.bom: affected < 7.3.3; fixed in 7.3.3

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

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.portal.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-mg53-xr8m-86hw (GitHub-reviewed advisory GHSA-mg53-xr8m-86hw lists affected ranges: Maven com.liferay.portal:release.portal.bom >=0 <7.3.3)

Commands are suggestions: review each one before running it.