Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

Liferay Portal and Liferay DXP fails to check origin of event messagesGHSA-ghw5-998m-vw4w

MEDIUMFix: liferay/liferay-portal@2fe1441

GHSA-ghw5-998m-vw4w is a medium-severity (CVSS 5.3) CWE-346 vulnerability in com.liferay:com.liferay.remote.app.web. A fix is available for com.liferay:com.liferay.remote.app.web — see the affected versions and patch details below.

Also known asBIT-liferay-2022-25146CVE-2022-25146
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs37th percentile — riskier than 37% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-ghw5-998m-vw4w by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

2 pkgs affected
☕com.liferay:com.liferay.remote.app.web☕com.liferay.portal:release.dxp.bom

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

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.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.liferay:com.liferay.remote.app.weball versions2.0.21com.liferay:com.liferay.remote.app.web:2.0.21
☕Mavencom.liferay.portal:release.dxp.bomall versions7.4.13.u5com.liferay.portal:release.dxp.bom:7.4.13.u5

Affected Products

2 products · 2 configurations
Application
digital experience platformliferay
≤ 7.4
range
Application
liferay portalliferay
≥ 7.4.3.4 && < 7.4.3.9
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.remote.app.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.liferay:com.liferay.remote.app.web to 2.0.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghw5-998m-vw4w is resolved across your whole dependency graph.

  3. 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.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-ghw5-998m-vw4w in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Liferay Portal and Liferay DXP fails to check origin of…