GHSA-vrwx-q9pj-x488 — com.liferay.portal.impl
MEDIUMGHSA-vrwx-q9pj-x488 is a medium-severity (CVSS 5.3) vulnerability in com.liferay.portal:com.liferay.portal.impl. A fix is available for com.liferay.portal:com.liferay.portal.impl — see the affected versions and patch details below.
Liferay Portal and Liferay DXP Bypass via Double Encoded URL
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-vrwx-q9pj-x488 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
com.liferay.portal:com.liferay.portal.impl☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.portal.bom☕com.liferay.portal:com.liferay.portal.implReal-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
In Liferay Portal before 7.3.1, com.liferay.portal:com.liferay.portal.impl before 7.1.3 and 7.4.0, Liferay Portal 6.2 EE, and Liferay DXP 7.2, DXP 7.1 and DXP 7.0, the property 'portlet.resource.id.banned.paths.regexp' can be bypassed with doubled encoded URLs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:com.liferay.portal.impl | ≥ 7.2.0&&< 7.4.0 | 7.4.0com.liferay.portal:com.liferay.portal.impl:7.4.0 |
| ☕Maven | com.liferay.portal:release.dxp.bom | all versions | 7.0.10.fp93com.liferay.portal:release.dxp.bom:7.0.10.fp93 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.1.0&&< 7.1.10.fp19 | 7.1.10.fp19com.liferay.portal:release.dxp.bom:7.1.10.fp19 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.2.0&&< 7.2.10.fp7 | 7.2.10.fp7com.liferay.portal:release.dxp.bom:7.2.10.fp7 |
| ☕Maven | com.liferay.portal:release.portal.bom | all versions | 7.3.1com.liferay.portal:release.portal.bom:7.3.1 |
| ☕Maven | com.liferay.portal:com.liferay.portal.impl | all versions | 7.1.3com.liferay.portal:com.liferay.portal.impl:7.1.3 |
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:com.liferay.portal.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:com.liferay.portal.impl to 7.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vrwx-q9pj-x488 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vrwx-q9pj-x488 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-vrwx-q9pj-x488. 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-vrwx-q9pj-x488 in your dependencies?
O3 Security finds GHSA-vrwx-q9pj-x488 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.