How severe is GHSA-cw79-fq4f-9r96?

No CVSS score has been assigned to GHSA-cw79-fq4f-9r96 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-cw79-fq4f-9r96?

GHSA-cw79-fq4f-9r96 affects the following packages: com.liferay:com.liferay.portal.security.ldap.impl (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cw79-fq4f-9r96?

Update com.liferay:com.liferay.portal.security.ldap.impl to 4.0.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cw79-fq4f-9r96 is resolved across your whole dependency graph.

How do I detect GHSA-cw79-fq4f-9r96 in my Maven dependencies?

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

How do I mitigate GHSA-cw79-fq4f-9r96 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-cw79-fq4f-9r96 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cw79-fq4f-9r96 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-cw79-fq4f-9r96?

GHSA-cw79-fq4f-9r96 has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 4th 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-cw79-fq4f-9r96?

GHSA-cw79-fq4f-9r96 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-cw79-fq4f-9r96 published, and has it been updated?

GHSA-cw79-fq4f-9r96 was published on October 27, 2025 and was last updated on November 15, 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 Vulnerable to Information Exposure Through a Log File Vulnerability in LDAP Import FeatureGHSA-cw79-fq4f-9r96

Fix: liferay/liferay-portal@fc14297

GHSA-cw79-fq4f-9r96 is a CWE-532 vulnerability in com.liferay:com.liferay.portal.security.ldap.impl. A fix is available for com.liferay:com.liferay.portal.security.ldap.impl — see the affected versions and patch details below.

Also known asCVE-2025-62262

Published

Oct 27, 2025

Updated

Nov 15, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 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-cw79-fq4f-9r96.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs4th percentile — riskier than 4% 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.portal.security.ldap.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

Information exposure through log file vulnerability in LDAP import feature in Liferay Portal 7.4.0 through 7.4.3.97, and older unsupported versions, and Liferay DXP 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows local users to view user email address in the log files.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.liferay:com.liferay.portal.security.ldap.impl`	≥ 4.0.2&&< 4.0.54	4.0.54`com.liferay:com.liferay.portal.security.ldap.impl:4.0.54`

Affected Products

2 products · 43 configurations

Application

digital experience platformliferay

6 versions

7.37.42023.q3.12023.q3.22023.q3.32023.q3.4

Application

liferay portalliferay

≥ 7.0.0 && < 7.4.3.98

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.portal.security.ldap.impl, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay:com.liferay.portal.security.ldap.impl to 4.0.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cw79-fq4f-9r96 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.