# CVE-2025-43759: Liferay Portal users are able to add system admin portlets to pages

> Admin users of a virtual instance can expose tenant lists, allowing any tenant to discover other tenants in the system.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Aug 2025
- **Updated:** 26 Aug 2025
- **Also known as:** GHSA-w3cr-3xw2-rp78

## What is CVE-2025-43759?

CVE-2025-43759 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 22 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Liferay Portal 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.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay:com.liferay.layout.impl` | Maven | All versions | 6.0.147 |
| `com.liferay:com.liferay.layout.impl` | Maven | All versions | 6.0.147 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

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

Upgrade com.liferay:com.liferay.layout.impl to 6.0.147 or later.

## Is CVE-2025-43759 being exploited?

There is no known exploitation of CVE-2025-43759 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-43759 and fix it if it is affected.

What it is: CVE-2025-43759 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 22 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-43759 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay:com.liferay.layout.impl (Maven): affected all versions; fixed in 6.0.147
- com.liferay:com.liferay.layout.impl (Maven): affected all versions; fixed in 6.0.147

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-43759/ (Markdown: https://insights.sbomify.com/CVE-2025-43759/index.md)
```

## Sources

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

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