How severe is GHSA-v32m-pf9q-p3xg?

GHSA-v32m-pf9q-p3xg has a CVSS score of 9.6/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-v32m-pf9q-p3xg?

GHSA-v32m-pf9q-p3xg affects the following packages: com.liferay.portal:release.portal.bom (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v32m-pf9q-p3xg?

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

How do I detect GHSA-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg?

O3 pinpoints whether GHSA-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg actively exploited in the wild?

No public exploit code has been indexed for GHSA-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg?

GHSA-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg published, and has it been updated?

GHSA-v32m-pf9q-p3xg was published on November 17, 2023 and was last updated on February 16, 2024. 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-v32m-pf9q-p3xg

CRITICAL

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

Liferay Portal XSS with `p_l_back_url_title` on edit content page

Also known asCVE-2023-47797

Published

Nov 17, 2023

Updated

Feb 16, 2024

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 on a content page’s edit page in Liferay Portal 7.4.3.94 through 7.4.3.95 allows remote attackers to inject arbitrary web script or HTML via the p_l_back_url_title parameter.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:release.portal.bom`	≥ 7.4.3.94&&< 7.4.3.96	7.4.3.96

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.96 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg 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-v32m-pf9q-p3xg. 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-v32m-pf9q-p3xg in your dependencies?

O3 detects GHSA-v32m-pf9q-p3xg 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