GHSA-chj2-4vg7-hhg3
CRITICALGHSA-chj2-4vg7-hhg3 is a critical-severity (CVSS 9.6) Cross-Site Request Forgery (CSRF) vulnerability in com.liferay.portal:release.portal.bom. O3 Security confirms whether GHSA-chj2-4vg7-hhg3 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console
Blast Radius
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☕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
The Script Console in Liferay Portal 7.0.0 through 7.4.3.101, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, 7.2 GA through fix pack 20, 7.1 GA through fix pack 28, 7.0 GA through fix pack 102 and 6.2 GA through fix pack 173 does not sufficiently protect against Cross-Site Request Forgery (CSRF) attacks, which allows remote attackers to execute arbitrary Groovy script via a crafted URL or a XSS vulnerability. This issue has been patched in Liferay Portal 7.4.3.102, Liferay DXP 2024.Q1.1, Liferay DXP 2023.Q4.0, Liferay DXP 2023.Q3.5, and Liferay DXP 7.3 Update 36.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:release.portal.bom | ≥ 7.0.0-a1&&< 7.4.3.102-GA102 | 7.4.3.102-GA102 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 2023.Q3.1&&< 2023.Q3.5 | 2023.Q3.5 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.0.0-GA | No fix |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.1.0-GA | No fix |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.2.0.GA | No fix |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.3.0-GA&&< 7.3.10.u36 | 7.3.10.u36 |
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.102-GA102 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-chj2-4vg7-hhg3 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-chj2-4vg7-hhg3 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-chj2-4vg7-hhg3. 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-chj2-4vg7-hhg3 in your dependencies?
O3 detects GHSA-chj2-4vg7-hhg3 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.