How severe is GHSA-xw6m-3m5q-mxpm?

No CVSS score has been assigned to GHSA-xw6m-3m5q-mxpm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xw6m-3m5q-mxpm?

GHSA-xw6m-3m5q-mxpm affects the following packages: com.liferay:com.liferay.account.admin.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xw6m-3m5q-mxpm?

Update com.liferay:com.liferay.account.admin.web to 2.0.114 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xw6m-3m5q-mxpm is resolved across your whole dependency graph.

How do I detect GHSA-xw6m-3m5q-mxpm in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.account.admin.web. 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.

How do I mitigate GHSA-xw6m-3m5q-mxpm if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-xw6m-3m5q-mxpm?

O3 pinpoints whether GHSA-xw6m-3m5q-mxpm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xw6m-3m5q-mxpm actively exploited in the wild?

No public exploit code has been indexed for GHSA-xw6m-3m5q-mxpm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xw6m-3m5q-mxpm?

GHSA-xw6m-3m5q-mxpm has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 10th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-xw6m-3m5q-mxpm published, and has it been updated?

GHSA-xw6m-3m5q-mxpm was published on October 10, 2025 and was last updated on October 11, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xw6m-3m5q-mxpm: com.liferay.account.admin… Cross-Site Scri…

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk10th percentile+0.17%

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.

Blast Radius

1 pkg affected

☕com.liferay:com.liferay.account.admin.web

Real-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 on the Membership page in Account Settings in Liferay Portal 7.4.3.21 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 21 through update 92 allows remote authenticated attackers to inject arbitrary web script or HTML via a crafted payload injected into a Account's “Name“ text field.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.account.admin.web`	≥ 2.0.40&&< 2.0.114	2.0.114

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.account.admin.web. 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:com.liferay.account.admin.web to 2.0.114 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xw6m-3m5q-mxpm 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-xw6m-3m5q-mxpm 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-xw6m-3m5q-mxpm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Stored cross-site scripting (XSS) vulnerability on the Membership page in Account Settings in Liferay Portal 7.4.3.21 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 21 through update 92 allows remote authenticated attackers to inject arbitrary web script or HTML via a crafted payload injected into a Account's “Name“ text field.

O3 Security · Impact-Aware SCA

Is GHSA-xw6m-3m5q-mxpm in your dependencies?

O3 detects GHSA-xw6m-3m5q-mxpm across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-xw6m-3m5q-mxpm