How severe is GHSA-2j97-4jmq-c4xf?

GHSA-2j97-4jmq-c4xf has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2j97-4jmq-c4xf?

GHSA-2j97-4jmq-c4xf affects the following packages: com.liferay.portal:release.portal.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-2j97-4jmq-c4xf?

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-2j97-4jmq-c4xf is resolved across your whole dependency graph.

How do I detect GHSA-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf?

O3 pinpoints whether GHSA-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf actively exploited in the wild?

No public exploit code has been indexed for GHSA-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf?

GHSA-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf published, and has it been updated?

GHSA-2j97-4jmq-c4xf was published on October 31, 2025 and was last updated on November 15, 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-2j97-4jmq-c4xf

MEDIUM

GHSA-2j97-4jmq-c4xf is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in com.liferay.portal:release.portal.bom. O3 Security confirms whether GHSA-2j97-4jmq-c4xf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Liferay Portal Vulnerable to Reflected XSS via the selectedLanguageId Parameter

Also known asCVE-2025-62264

Published

Oct 31, 2025

Updated

Nov 15, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

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

Reflected cross-site scripting (XSS) vulnerability in Languauge Override in Liferay Portal 7.4.3.8 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, and 7.4 update 4 through update 92 allows remote attackers to inject arbitrary web script or HTML via the _com_liferay_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.3.8&&< 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-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf 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-2j97-4jmq-c4xf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Reflected cross-site scripting (XSS) vulnerability in Languauge Override in Liferay Portal 7.4.3.8 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, and 7.4 update 4 through update 92 allows remote attackers to inject arbitrary web script or HTML via the `_com_liferay_portal_language_override_web_internal_portlet_PLOPortlet_selectedLanguageId` parameter.

O3 Security · Impact-Aware SCA

Is GHSA-2j97-4jmq-c4xf in your dependencies?

O3 detects GHSA-2j97-4jmq-c4xf 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