Liferay Portal and Liferay DXP fails to check origin of event messages

Exploitation

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

CVSS

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

EPSS

• CVE-2022-25146: 0.45% estimated exploitation activity in the next 30 days; percentile 39.34 (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 Remote App module before 2.0.21 from Liferay Portal v7.4.3.4 through v7.4.3.8 and Liferay DXP 7.4 before update 5 does not check if the origin of event messages it receives matches the origin of the Remote App, allowing attackers to exfiltrate the CSRF token via a crafted event message.

Published by the source

4 Mar 2022, 00:00 UTC

Last modified by the source

15 Jul 2025, 19:02 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ghw5-998m-vw4w

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

# Patch Next advisory brief: CVE-2022-25146

Advisory: Liferay Portal and Liferay DXP fails to check origin of event messages
IDs: CVE-2022-25146, GHSA-ghw5-998m-vw4w
Record: https://patchnext.com/advisories/cve-2022-25146 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay:com.liferay.remote.app.web 2.0.21; com.liferay.portal:release.dxp.bom 7.4.13.u5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay:com.liferay.remote.app.web: affected < 2.0.21; fixed in 2.0.21
- Maven com.liferay.portal:release.dxp.bom: affected < 7.4.13.u5; fixed in 7.4.13.u5

## Suggested inspection (read-only)
- Maven com.liferay:com.liferay.remote.app.web: 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
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:com.liferay.remote.app.web, 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-ghw5-998m-vw4w (GitHub-reviewed advisory GHSA-ghw5-998m-vw4w lists affected ranges: Maven com.liferay:com.liferay.remote.app.web >=0 =0 <7.4.13.u5)

Commands are suggestions: review each one before running it.