How severe is GHSA-m4g9-5mg6-gfr3?

No CVSS score has been assigned to GHSA-m4g9-5mg6-gfr3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m4g9-5mg6-gfr3?

GHSA-m4g9-5mg6-gfr3 affects the following packages: com.liferay.commerce:com.liferay.commerce.order.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-m4g9-5mg6-gfr3?

Update com.liferay.commerce:com.liferay.commerce.order.web to 5.0.101 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4g9-5mg6-gfr3 is resolved across your whole dependency graph.

How do I detect GHSA-m4g9-5mg6-gfr3 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.commerce:com.liferay.commerce.order.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m4g9-5mg6-gfr3 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-m4g9-5mg6-gfr3?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m4g9-5mg6-gfr3 can be triaged on real exposure rather than presence alone.

Is GHSA-m4g9-5mg6-gfr3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4g9-5mg6-gfr3 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-m4g9-5mg6-gfr3?

GHSA-m4g9-5mg6-gfr3 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th 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.

What type of vulnerability is GHSA-m4g9-5mg6-gfr3?

GHSA-m4g9-5mg6-gfr3 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m4g9-5mg6-gfr3 published, and has it been updated?

GHSA-m4g9-5mg6-gfr3 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.

☕ Maven

Not in CISA KEV

GHSA-m4g9-5mg6-gfr3 — com.liferay.commerce.orde…

Fix: liferay/liferay-portal@e6d49ed

GHSA-m4g9-5mg6-gfr3 is a Cross-site Scripting (XSS) vulnerability in com.liferay.commerce:com.liferay.commerce.order.web. A fix is available for com.liferay.commerce:com.liferay.commerce.order.web — see the affected versions and patch details below.

Liferay Portal Commerce is vulnerable to XSS through account "name" field

Also known asCVE-2025-62237

Published

Oct 10, 2025

Updated

Oct 11, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-m4g9-5mg6-gfr3.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

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.

Real-World Exposure

1 pkg affected

☕com.liferay.commerce:com.liferay.commerce.order.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 in Commerce’s view order page in Liferay Portal 7.4.3.8 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 8 through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into an Account’s “Name” text field.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.commerce:com.liferay.commerce.order.web`	≥ 5.0.29&&< 5.0.101	5.0.101`com.liferay.commerce:com.liferay.commerce.order.web:5.0.101`

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.commerce:com.liferay.commerce.order.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.commerce:com.liferay.commerce.order.web to 5.0.101 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m4g9-5mg6-gfr3 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-m4g9-5mg6-gfr3 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m4g9-5mg6-gfr3. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-m4g9-5mg6-gfr3 in your dependencies?

O3 Security finds GHSA-m4g9-5mg6-gfr3 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works