# CVE-2025-43743: Liferay Portal Enumeration Discrepancy in Calendars

> Authenticated users can enumerate other users' names via calendar access, enabling targeted phishing attacks against Liferay Portal and DXP users.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2025
- **Updated:** 19 Aug 2025
- **Also known as:** GHSA-g4vp-4gqr-7v8c

## What is CVE-2025-43743?

CVE-2025-43743 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.5, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.1 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.15 and 7.4 GA through update 92 allows any authenticated remote user to view other calendars by allowing them to enumerate the names of other users, given an attacker the possibility to send phishing to these users.

Weakness: CWE-203 (Observable Discrepancy)

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

2 open source packages ship an affected version, including com.liferay.portal:release.portal.bom. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.4.0-ga1 to 7.4.3.132-ga132 | None |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.4.0-ga1 to 7.4.3.132-ga132 | None |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

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

No fix has been published for CVE-2025-43743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-43743 being exploited?

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

What it is: CVE-2025-43743 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 19 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-43743 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.portal.bom (Maven): affected from 7.4.0-ga1 up to 7.4.3.132-ga132; no fix listed
- com.liferay.portal:release.portal.bom (Maven): affected from 7.4.0-ga1 up to 7.4.3.132-ga132; no fix listed

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

## Sources

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

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