How severe is GHSA-p73j-gpcq-49h8?

No CVSS score has been assigned to GHSA-p73j-gpcq-49h8 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p73j-gpcq-49h8?

GHSA-p73j-gpcq-49h8 affects the following packages: com.liferay:com.liferay.server.admin.web (Maven), com.liferay:com.liferay.server.admin.web (Maven), com.liferay:com.liferay.server.admin.web (Maven), com.liferay:com.liferay.server.admin.web (Maven), com.liferay:com.liferay.server.admin.web (Maven). Ecosystems affected: Maven.

How do I fix GHSA-p73j-gpcq-49h8?

Update com.liferay:com.liferay.server.admin.web to 5.0.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p73j-gpcq-49h8 is resolved across your whole dependency graph.

How do I detect GHSA-p73j-gpcq-49h8 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay:com.liferay.server.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-p73j-gpcq-49h8 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-p73j-gpcq-49h8?

O3 pinpoints whether GHSA-p73j-gpcq-49h8 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-p73j-gpcq-49h8 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p73j-gpcq-49h8 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-p73j-gpcq-49h8?

GHSA-p73j-gpcq-49h8 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 43th 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-p73j-gpcq-49h8?

GHSA-p73j-gpcq-49h8 is classified as Path Traversal (CWE-22). 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-p73j-gpcq-49h8 published, and has it been updated?

GHSA-p73j-gpcq-49h8 was published on June 16, 2025 and was last updated on June 16, 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

GHSA-p73j-gpcq-49h8

Liferay Portal path traversal vulnerability with the downloading and installation of Xuggler

Also known asCVE-2025-3594

Published

Jun 16, 2025

Updated

Jun 16, 2025

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk43th percentile-1.02%

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

5 pkgs affected

☕com.liferay:com.liferay.server.admin.web☕com.liferay:com.liferay.server.admin.web☕com.liferay:com.liferay.server.admin.web☕com.liferay:com.liferay.server.admin.web☕com.liferay:com.liferay.server.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

Path traversal vulnerability with the downloading and installation of Xuggler in Liferay Portal 7.0.0 through 7.4.3.4, and Liferay DXP 7.4 GA, 7.3 GA through update 34, and older unsupported versions allows remote attackers to (1) add files to arbitrary locations on the server and (2) download and execute arbitrary files from the download server via the _com_liferay_server_admin_web_portlet_ServerAdminPortlet_jarName parameter.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.server.admin.web`	≥ 5.0.0&&< 5.0.24	5.0.24
☕Maven	`com.liferay:com.liferay.server.admin.web`	≥ 4.0.0&&< 4.0.48	4.0.48
☕Maven	`com.liferay:com.liferay.server.admin.web`	≥ 3.0.0&&< 3.0.67	3.0.67
☕Maven	`com.liferay:com.liferay.server.admin.web`	≥ 2.0.0&&< 2.0.66	2.0.66
☕Maven	`com.liferay:com.liferay.server.admin.web`	all versions	1.0.93

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.server.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.server.admin.web to 5.0.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p73j-gpcq-49h8 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-p73j-gpcq-49h8 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-p73j-gpcq-49h8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Path traversal vulnerability with the downloading and installation of Xuggler in Liferay Portal 7.0.0 through 7.4.3.4, and Liferay DXP 7.4 GA, 7.3 GA through update 34, and older unsupported versions allows remote attackers to (1) add files to arbitrary locations on the server and (2) download and execute arbitrary files from the download server via the `_com_liferay_server_admin_web_portlet_ServerAdminPortlet_jarName` parameter.

O3 Security · Impact-Aware SCA

Is GHSA-p73j-gpcq-49h8 in your dependencies?

O3 detects GHSA-p73j-gpcq-49h8 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