How severe is GHSA-h4m4-xp33-37mj?

No CVSS score has been assigned to GHSA-h4m4-xp33-37mj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h4m4-xp33-37mj?

GHSA-h4m4-xp33-37mj affects the following packages: com.liferay.portal:com.liferay.portal.kernel (Maven). Ecosystems affected: Maven.

How do I fix GHSA-h4m4-xp33-37mj?

Update com.liferay.portal:com.liferay.portal.kernel to 155.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4m4-xp33-37mj is resolved across your whole dependency graph.

How do I detect GHSA-h4m4-xp33-37mj in my Maven dependencies?

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

How do I mitigate GHSA-h4m4-xp33-37mj 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-h4m4-xp33-37mj?

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

Is GHSA-h4m4-xp33-37mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-h4m4-xp33-37mj 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-h4m4-xp33-37mj?

GHSA-h4m4-xp33-37mj has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th 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-h4m4-xp33-37mj?

GHSA-h4m4-xp33-37mj 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-h4m4-xp33-37mj published, and has it been updated?

GHSA-h4m4-xp33-37mj was published on August 23, 2025 and was last updated on August 25, 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-h4m4-xp33-37mj — com.liferay.portal.kernel

Fix: liferay/liferay-portal@a712758

GHSA-h4m4-xp33-37mj is a Cross-site Scripting (XSS) vulnerability in com.liferay.portal:com.liferay.portal.kernel. A fix is available for com.liferay.portal:com.liferay.portal.kernel — see the affected versions and patch details below.

Liferay Portal vulnerable to Reflected XSS with the referer and forward parameter

Also known asCVE-2025-43770

Published

Aug 23, 2025

Updated

Aug 25, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-h4m4-xp33-37mj.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% 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.portal:com.liferay.portal.kernel

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

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.131, and Liferay DXP 2024.Q4.0 through 2024.Q4.3, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12 and 7.4 GA through update 92 allows an remote non-authenticated attacker to inject JavaScript into the referer or FORWARD_URL using %00 in those parameters.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay.portal:com.liferay.portal.kernel`	all versions	155.0.0`com.liferay.portal:com.liferay.portal.kernel:155.0.0`

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.portal:com.liferay.portal.kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.portal:com.liferay.portal.kernel to 155.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4m4-xp33-37mj 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-h4m4-xp33-37mj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-h4m4-xp33-37mj. 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-h4m4-xp33-37mj in your dependencies?

O3 Security finds GHSA-h4m4-xp33-37mj 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