GHSA-p63m-vmjr-wg37
HIGHGHSA-p63m-vmjr-wg37 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in com.liferay.portal:release.portal.bom. O3 Security confirms whether GHSA-p63m-vmjr-wg37 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Liferay Portal and Liferay DXP Vulnerable to Cross-Site Request Forgery (CSRF) via the Content Page Editor
Real-World Exposure
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.bomReal-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 request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.3.2 through 7.4.3.107, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, 2023.Q3.1 through 2023.Q3.5, 7.4 GA through update 92 and 7.3 GA through update 35 allows remote attackers to (1) change user passwords, (2) shut down the server, (3) execute arbitrary code in the scripting console, (4) and perform other administrative actions via the p_l_back_url parameter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:release.portal.bom | ≥ 7.3.2&&< 7.4.3.108 | 7.4.3.108 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 2023.Q4.0&&< 2023.Q4.3 | 2023.Q4.3 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 2023.Q3.1&&< 2023.Q3.6 | 2023.Q3.6 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.3.GA&&< 7.3u36 | 7.3u36 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.4.GA&&< 7.4u93 | 7.4u93 |
Detection & mitigation playbook
Open-source dependencyDetect
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.108 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p63m-vmjr-wg37 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-p63m-vmjr-wg37 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-p63m-vmjr-wg37. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p63m-vmjr-wg37 in your dependencies?
O3 detects GHSA-p63m-vmjr-wg37 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.