How severe is GHSA-w3cr-3xw2-rp78?

No CVSS score has been assigned to GHSA-w3cr-3xw2-rp78 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w3cr-3xw2-rp78?

GHSA-w3cr-3xw2-rp78 affects the following packages: com.liferay:com.liferay.layout.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w3cr-3xw2-rp78?

Update com.liferay:com.liferay.layout.impl to 6.0.147 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3cr-3xw2-rp78 is resolved across your whole dependency graph.

How do I detect GHSA-w3cr-3xw2-rp78 in my Maven dependencies?

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

How do I mitigate GHSA-w3cr-3xw2-rp78 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.

Is GHSA-w3cr-3xw2-rp78 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w3cr-3xw2-rp78 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-w3cr-3xw2-rp78?

GHSA-w3cr-3xw2-rp78 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th 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-w3cr-3xw2-rp78?

GHSA-w3cr-3xw2-rp78 is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w3cr-3xw2-rp78 published, and has it been updated?

GHSA-w3cr-3xw2-rp78 was published on August 22, 2025 and was last updated on December 20, 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

Liferay Portal users are able to add system admin portlets to pagesGHSA-w3cr-3xw2-rp78

Fix: liferay/liferay-portal@2e29e67

GHSA-w3cr-3xw2-rp78 is a CWE-732 vulnerability in com.liferay:com.liferay.layout.impl. A fix is available for com.liferay:com.liferay.layout.impl — see the affected versions and patch details below.

Also known asCVE-2025-43759

Published

Aug 22, 2025

Updated

Dec 20, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-w3cr-3xw2-rp78.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.liferay:com.liferay.layout.impl

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

Liferay Portal versions 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.14 and 7.4 GA through update 92 allows admin users of a virtual instance to add pages that are not in the default/main virtual instance, then any tenant can create a list of all other tenants.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.layout.impl`	all versions	6.0.147`com.liferay:com.liferay.layout.impl:6.0.147`

Affected Products

2 products · 7 configurations

Application

digital experience platformliferay

≥ 2024.q4.0 && ≤ 2024.q4.7

2 versions

7.42025.q1.0

Application

liferay portalliferay

≥ 7.4.0 && ≤ 7.4.3.132

range

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.layout.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.layout.impl to 6.0.147 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3cr-3xw2-rp78 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.