GHSA-vwj8-4grf-3r8v is a high-severity (CVSS 7.5) CWE-613 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 fails to invalidate password reset tokens after use
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-vwj8-4grf-3r8v 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 378,156 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.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
In implementation for the portal services before 5.7.3 in Liferay Portal 7.3.0 and earlier, and Liferay DXP 7.0 before fix pack 96, 7.1 before fix pack 18, and 7.2 before fix pack 5, password reset tokens are not invalidated after a user changes their password, which allows remote attackers to change the user’s password via the old password reset token.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.portal:com.liferay.portal.impl | all versions | 5.7.3com.liferay.portal:com.liferay.portal.impl:5.7.3 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.0.0&&< 7.0.10.fp96 | 7.0.10.fp96com.liferay.portal:release.dxp.bom:7.0.10.fp96 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.1.0&&< 7.1.10.fp18 | 7.1.10.fp18com.liferay.portal:release.dxp.bom:7.1.10.fp18 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.2.0&&< 7.2.10.fp5 | 7.2.10.fp5com.liferay.portal:release.dxp.bom:7.2.10.fp5 |
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 5.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vwj8-4grf-3r8v 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-vwj8-4grf-3r8v can be triaged on real exposure rather than presence alone.
Tailored to GHSA-vwj8-4grf-3r8v. 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-vwj8-4grf-3r8v in your dependencies?
O3 Security finds GHSA-vwj8-4grf-3r8v across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.