# CVE-2025-43825: Liferay Portal exposes sensitive user data through its Freemarker template

> An unauthorized actor can access sensitive user data exposed in Freemarker templates, leading to potential disclosure of confidential information.

- **Severity:** Medium 4.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:A/VC:L/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:** 3 Oct 2025
- **Updated:** 6 Oct 2025
- **Also known as:** GHSA-rggc-gf6w-9q73

## What is CVE-2025-43825?

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

### Official description

A vulnerability in Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.4, 2024.Q4.0 through 2024.Q4.5, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.1 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.12, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows sensitive user data to be included in the Freemarker template. This weakness permits an unauthorized actor to gain access to, and potentially render, confidential information that should remain restricted.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay:com.liferay.portal.template.freemarker` | Maven | From 7.0.3 | 7.0.60 |
| `com.liferay:com.liferay.portal.template.freemarker` | Maven | From 7.0.3 | 7.0.60 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

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

Upgrade com.liferay:com.liferay.portal.template.freemarker to 7.0.60 or later.

## Is CVE-2025-43825 being exploited?

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

What it is: CVE-2025-43825 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 3 Oct 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-43825 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay:com.liferay.portal.template.freemarker (Maven): affected from 7.0.3; fixed in 7.0.60
- com.liferay:com.liferay.portal.template.freemarker (Maven): affected from 7.0.3; fixed in 7.0.60

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

## Sources

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

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