# CVE-2025-62262: Liferay Portal Vulnerable to Information Exposure Through a Log File Vulnerability in LDAP Import Feature

> Local users can view user email addresses in log files due to information exposure in the LDAP import feature of Liferay Portal.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-cw79-fq4f-9r96

## What is CVE-2025-62262?

CVE-2025-62262 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2025-62262?

2 open source packages ship an affected version, including com.liferay:com.liferay.portal.security.ldap.impl. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay:com.liferay.portal.security.ldap.impl` | Maven | From 4.0.2 | 4.0.54 |
| `com.liferay:com.liferay.portal.security.ldap.impl` | Maven | From 4.0.2 | 4.0.54 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2025-62262?

Upgrade com.liferay:com.liferay.portal.security.ldap.impl to 4.0.54 or later.

## Is CVE-2025-62262 being exploited?

There is no known exploitation of CVE-2025-62262 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Digital Experience Platform

- [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6)
- [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6)
- [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)
- [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62262 and fix it if it is affected.

What it is: CVE-2025-62262 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 27 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62262 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay:com.liferay.portal.security.ldap.impl (Maven): affected from 4.0.2; fixed in 4.0.54
- com.liferay:com.liferay.portal.security.ldap.impl (Maven): affected from 4.0.2; fixed in 4.0.54

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62262/ (Markdown: https://insights.sbomify.com/CVE-2025-62262/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62262
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62262
- OSV: https://osv.dev/vulnerability/CVE-2025-62262

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62262/
Summaries are generated and may contain mistakes; the official description above is the record.