How severe is GHSA-hrc4-p2h3-pjqw?

No CVSS score has been assigned to GHSA-hrc4-p2h3-pjqw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hrc4-p2h3-pjqw?

GHSA-hrc4-p2h3-pjqw affects the following packages: com.liferay.portal:release.dxp.bom (Maven), 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), com.liferay.portal:release.dxp.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-hrc4-p2h3-pjqw?

No patched version of com.liferay.portal:release.dxp.bom has shipped for GHSA-hrc4-p2h3-pjqw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-hrc4-p2h3-pjqw in my Maven dependencies?

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

How do I mitigate GHSA-hrc4-p2h3-pjqw 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-hrc4-p2h3-pjqw?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hrc4-p2h3-pjqw can be triaged on real exposure rather than presence alone.

Is GHSA-hrc4-p2h3-pjqw actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrc4-p2h3-pjqw 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 is the EPSS score for GHSA-hrc4-p2h3-pjqw?

GHSA-hrc4-p2h3-pjqw has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hrc4-p2h3-pjqw?

GHSA-hrc4-p2h3-pjqw 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-hrc4-p2h3-pjqw published, and has it been updated?

GHSA-hrc4-p2h3-pjqw was published on March 19, 2025 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-hrc4-p2h3-pjqw — release.dxp.bom

GHSA-hrc4-p2h3-pjqw is a Cross-site Scripting (XSS) vulnerability in com.liferay.portal:release.dxp.bom. A fix is available for com.liferay.portal:release.dxp.bom — see the affected versions and patch details below.

Liferay Portal and Liferay DXP Vulnerable to Cross-Site Scripting (XSS)

Also known asCVE-2025-2536

Published

Mar 19, 2025

Updated

Sep 10, 2026

Affected

6 pkgs

Patched

5 / 6

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hrc4-p2h3-pjqw.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

6 pkgs affected

☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.portal.bom☕com.liferay.portal:release.dxp.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 on Liferay Portal 7.4.3.82 through 7.4.3.128, and Liferay DXP 2024.Q3.0, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 update 82 through update 92 in the Frontend JS module's layout-taglib/liferay/index.js allows remote attackers to inject arbitrary web script or HTML via toastData parameter

Affected Packages

6 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q2.0	No fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.3.82&&< 7.4.3.129	7.4.3.129`com.liferay.portal:release.portal.bom:7.4.3.129`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q1.1&&< 2024.Q1.13	2024.Q1.13`com.liferay.portal:release.dxp.bom:2024.Q1.13`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2023.Q4.0&&< 2024.Q4.0	2024.Q4.0`com.liferay.portal:release.dxp.bom:2024.Q4.0`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2023.Q3.1&&< 2024.Q4.0	2024.Q4.0`com.liferay.portal:release.dxp.bom:2024.Q4.0`
☕Maven	`com.liferay.portal:release.dxp.bom`	≥ 2024.Q3.0&&< 2024.Q3.1	2024.Q3.1`com.liferay.portal:release.dxp.bom:2024.Q3.1`

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.dxp.bom, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of com.liferay.portal:release.dxp.bom has shipped for GHSA-hrc4-p2h3-pjqw yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hrc4-p2h3-pjqw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hrc4-p2h3-pjqw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability on Liferay Portal 7.4.3.82 through 7.4.3.128, and Liferay DXP 2024.Q3.0, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 update 82 through update 92 in the Frontend JS module's layout-taglib/__liferay__/index.js allows remote attackers to inject arbitrary web script or HTML via toastData parameter

O3 Security · Impact-Aware SCA

Is GHSA-hrc4-p2h3-pjqw in your dependencies?

O3 Security finds GHSA-hrc4-p2h3-pjqw across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works