How severe is GHSA-rwhv-hvj2-qrqm?

GHSA-rwhv-hvj2-qrqm has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-rwhv-hvj2-qrqm?

GHSA-rwhv-hvj2-qrqm affects the following packages: com.liferay.portal:release.portal.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven), com.liferay.portal:release.dxp.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-rwhv-hvj2-qrqm?

Update com.liferay.portal:release.portal.bom to 7.4.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwhv-hvj2-qrqm is resolved across your whole dependency graph.

How do I detect GHSA-rwhv-hvj2-qrqm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.portal:release.portal.bom. 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-rwhv-hvj2-qrqm 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-rwhv-hvj2-qrqm?

O3 pinpoints whether GHSA-rwhv-hvj2-qrqm 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-rwhv-hvj2-qrqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-rwhv-hvj2-qrqm 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-rwhv-hvj2-qrqm?

GHSA-rwhv-hvj2-qrqm is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-rwhv-hvj2-qrqm published, and has it been updated?

GHSA-rwhv-hvj2-qrqm was published on February 21, 2024 and was last updated on January 28, 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

GHSA-rwhv-hvj2-qrqm

CRITICAL

GHSA-rwhv-hvj2-qrqm is a critical-severity (CVSS 9.6) Cross-site Scripting (XSS) vulnerability in com.liferay.portal:release.portal.bom. O3 Security confirms whether GHSA-rwhv-hvj2-qrqm is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting

Also known asCVE-2024-26269

Published

Feb 21, 2024

Updated

Jan 28, 2025

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Real-World Exposure

4 pkgs affected

☕com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕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

Cross-site scripting (XSS) vulnerability in the Frontend JS module's portlet.js in Liferay Portal 7.2.0 through 7.4.3.37, and Liferay DXP 7.4 before update 38, 7.3 before update 11, 7.2 before fix pack 20, and older unsupported versions allows remote attackers to inject arbitrary web script or HTML via the anchor (hash) part of a URL.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.2.0&&< 7.4.3.38	7.4.3.38
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.4.13.u1&&< 7.4.13.u38	7.4.13.u38
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.3.10.ep3&&< 7.3.10.u11	7.3.10.u11
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 7.2.0&&< 7.2.10.fp20	7.2.10.fp20

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.portal:release.portal.bom. 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.portal:release.portal.bom to 7.4.3.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwhv-hvj2-qrqm 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-rwhv-hvj2-qrqm 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-rwhv-hvj2-qrqm. 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-rwhv-hvj2-qrqm in your dependencies?

O3 detects GHSA-rwhv-hvj2-qrqm 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