Digital Experience PlatformApplication · Liferay

CVE-2025-43825

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-03

Fix available

A fix is available. Upgrade to 2024.Q1.13 / 2024.Q4.6 or later.

See remediation →

71/100

Remediation priority · Elevated

Remotely reachable Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · moderate confidence

Laravel Portal and DXP fail to properly restrict sensitive user data from being included in Freemarker templates, allowing unauthenticated attackers to potentially access and render confidential user information through template manipulation.

MitigationUpgrade Liferay Portal to version 7.4.3.133 or later, or apply the relevant patch for affected DXP quarterly releases. Review custom Freemarker templates to ensure they do not expose sensitive user data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Digital Experience PlatformApplication

Affected:>= 2023.Q3.1, <= 2023.Q3.10>= 2023.q4.0, <= 2023.q4.10>= 2024.Q1.1, < 2024.Q1.13>= 2024.Q2.1, <= 2024.Q2.13>= 2024.Q3.0, <= 2024.Q3.13>= 2024.Q4.0, < 2024.Q4.6>= 2025.Q1.1, < 2025.Q1.4= 7.4

Liferay PortalApplication

Affected:>= 7.4.0, <= 7.4.3.132

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Liferer Portal version

Locate the portal-ext.properties or portal-setup-wizard.properties file in your Liferer installation directory and check the 'product.cfg' or 'build.number' property, or check the OSGi bundle version via the Gogo shell command 'lb | grep com/liferay/portal'

Affected if The installed version falls within any of these ranges: 7.4.0 to 7.4.3.132; 2023.Q3.1 to 2023.Q3.10; 2023.Q4.0 to 2023.Q4.10; 2024.Q1.1 to 2024.Q1.12; 2024.Q2.1 to 2024.Q2.13; 2024.Q3.0 to 2024.Q3.13; 2024.Q4.0 to 2024.Q4.5; 2025.Q1.1 to 2025.Q1.3
Confirm Freemarker template engine is enabled

Check the Liferer control panel under Configuration > System Settings > Template Engines, or inspect the com_liferay_template_engine_[internal] configuration file for the Freemarker engine entry

Affected if Freemarker is listed as an enabled template engine
Locate custom Freemarker templates

Search the deployment directory and source repositories for .ftl files, typically found under /templates/ or /webapp/*/templates/ within theme or hook modules

Affected if Any custom .ftl template files exist in the Liferer deployment
Inspect templates for user data variables

Open each custom Freemarker template and search for variables that reference user objects such as $user, $userData, $contact, $emailAddress, $firstName, $lastName, $phoneNumber, $address, or similar personal information fields

Affected if A template references or outputs user-related personal data without access controls
Check template permissions configuration

Review the template configuration in the Liferer control panel under Content > Web Content > Structures or via the API endpoint /api/jsonws/template/get-templates to verify if template-level permissions are enforced

Affected if Permissions are not explicitly restricted on templates that expose user data, or anonymous users can access templates containing sensitive user fields

You are affected if your Liferer Portal version is within the affected ranges listed AND Freemarker templates are enabled AND those templates contain or could expose sensitive user data to unauthenticated access.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2024.Q1.13 / 2024.Q4.6 / 2025.Q1.4 or later

Fixed in 2024.Q1.132024.Q4.62025.Q1.4

Interim mitigation

Upgrade Liferay Portal to version 7.4.3.133 or later, or apply the relevant patch for affected DXP quarterly releases. Review custom Freemarker templates to ensure they do not expose sensitive user data.

Recommended fix Moderate confidence

Latest available fixed version per your product line (e.g., LPortal 7.4.3.133+, DXP 2024.Q1.13+, DXP 2024.Q2.14+, DXP 2024.Q3.14+, DXP 2024.Q4.6+, DXP 2025.Q1.5+)

1. Identify your current Lifford Portal or Digital Experience Platform version from the affected versions list.
2. For LPortal 7.4.x users: Upgrade to LPortal 7.4.3.133 or later, or the latest 7.4.x update available.
3. For DXP 2023.Q3.x users: Upgrade to 2023.Q3.11 or later.
4. For DXP 2023.Q4.x users: Upgrade to 2023.Q4.11 or later.
5. For DXP 2024.Q1.x users: Upgrade to 2024.Q1.13 or later.
6. For DXP 2024.Q2.x users: Upgrade to 2024.Q2.14 or later.
7. For DXP 2024.Q3.x users: Upgrade to 2024.Q3.14 or later.
8. For DXP 2024.Q4.x users: Upgrade to 2024.Q4.6 or later.

Caveat Standard upgrade considerations apply - review Lifford compatibility matrix and test in non-production environment before deploying

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA4.0 h

22.0 hours of engineering $3,860

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-43825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

liferay.devVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43825 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-43825?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsUpgrade to 2024.Q1.13 / 2024.Q4.6 or later

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Digital Experience Platform

Remediation

Need this fixed?

Fix this in Digital Experience Platform 22 hrs · Moderate

Typical engagement from $3,860

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-43825 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References