GHSA-7m65-hmvg-rxpc is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in com.liferay:com.liferay.site.memberships.web. A fix is available for com.liferay:com.liferay.site.memberships.web — see the affected versions and patch details below.
Liferay Portal and Liferay DXP Vulnerable to XSS in the Site Module
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7m65-hmvg-rxpc.
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-7m65-hmvg-rxpc 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 379,842 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:com.liferay.site.memberships.web☕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
Stored cross-site scripting (XSS) vulnerability in the Site module's user membership administration page in Liferay Site Memberships Web before 5.0.10 from Liferay Portal (7.0.1 through 7.4.1), and Liferay DXP 7.0 before fix pack 102, 7.1 before fix pack 26, 7.2 before fix pack 15, and 7.3 before service pack 3 allows remote attackers to inject arbitrary web script or HTML via the a user's name.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay:com.liferay.site.memberships.web | all versions | 5.0.10com.liferay:com.liferay.site.memberships.web:5.0.10 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.0.0&&< 7.0.10.fp102 | 7.0.10.fp102com.liferay.portal:release.dxp.bom:7.0.10.fp102 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.1.0&&< 7.1.10.fp26 | 7.1.10.fp26com.liferay.portal:release.dxp.bom:7.1.10.fp26 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.2.0&&< 7.2.10.fp15 | 7.2.10.fp15com.liferay.portal:release.dxp.bom:7.2.10.fp15 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.site.memberships.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.site.memberships.web to 5.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m65-hmvg-rxpc is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7m65-hmvg-rxpc can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7m65-hmvg-rxpc. 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-7m65-hmvg-rxpc in your dependencies?
O3 Security finds GHSA-7m65-hmvg-rxpc across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.