How severe is GHSA-xx7h-2wf7-hc7p?

No CVSS score has been assigned to GHSA-xx7h-2wf7-hc7p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xx7h-2wf7-hc7p?

GHSA-xx7h-2wf7-hc7p affects the following packages: com.liferay.portal:release.portal.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xx7h-2wf7-hc7p?

Update com.liferay.portal:release.portal.bom to 7.4.3.112-ga112 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xx7h-2wf7-hc7p is resolved across your whole dependency graph.

How do I detect GHSA-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p?

O3 pinpoints whether GHSA-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p actively exploited in the wild?

No public exploit code has been indexed for GHSA-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p?

GHSA-xx7h-2wf7-hc7p has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th 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-xx7h-2wf7-hc7p?

GHSA-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p published, and has it been updated?

GHSA-xx7h-2wf7-hc7p was published on October 8, 2025 and was last updated on December 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xx7h-2wf7-hc7p: release.portal.bom Cross-Site Scripting

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk10th percentile+0.17%

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.

Blast Radius

1 pkg affected

☕com.liferay.portal:release.portal.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 Commerce Search Result widget in Liferay Portal 7.4.0 through 7.4.3.111, and Liferay DXP 2023.Q4 before patch 6, 2023.Q3 before patch 9, and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a Commerce Product's Name text field.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.0&&< 7.4.3.112-ga112	7.4.3.112-ga112

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.112-ga112 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p 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-xx7h-2wf7-hc7p. 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 in the Commerce Search Result widget in Liferay Portal 7.4.0 through 7.4.3.111, and Liferay DXP 2023.Q4 before patch 6, 2023.Q3 before patch 9, and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a Commerce Product's Name text field.

O3 Security · Impact-Aware SCA

Is GHSA-xx7h-2wf7-hc7p in your dependencies?

O3 detects GHSA-xx7h-2wf7-hc7p 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

GHSA-xx7h-2wf7-hc7p