Digital Experience PlatformApplication · Liferay

CVE-2025-43749

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-20

Fix available

A fix is available. Upgrade to 2024.Q1.15 / 2025.Q1.2 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q1.0 through 2025.Q1.1, 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.14 and 7.4 GA through update 92 allows unauthenticated users (guests) to access via URL files uploaded in the form and stored in document_library

Technical summary

dbcve analysis · high confidence

Lifera Portal and DXP allow unauthenticated (guest) users to access files that were uploaded through forms and stored in the document_library via direct URLs. This is an insecure direct object reference (IDOR) or improper authorization vulnerability where access controls on uploaded documents are not properly enforced, permitting unauthorized access to sensitive files.

MitigationApply the vendor security patches for the affected versions (7.4.0-7.4.3.132 for Portal, and the listed DXP versions). Additionally, review and enforce proper document_library folder permissions to ensure guest users cannot access files they did not upload.

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:>= 2024.Q1.1, < 2024.Q1.15>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.2= 7.4

Liferay PortalApplication

Affected:>= 7.4.0, <= 7.4.3.132

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify the installed Lifer Portal or DXP version

Locate the version number in the Lifer administration console under Control Panel > Configuration > Server Information, or check the bundle's version.properties file in the Lifer home directory

Affected if The installed version falls within one of these ranges: 7.4.0 to 7.4.3.132 for Portal; 2024.Q1.1 to 2024.Q1.15; 2024.q2.0 to 2024.q2.13; 2024.q3.1 to 2024.q3.13; 2024.q4.0 to 2024.q4.7; or 2025.Q1.0 to 2025.Q1.1 for DXP
Confirm document_library is in use

Navigate to the Lifer administration panel and check if any Documents and Media folders exist, or search for the document_library module in the OSGi console

Affected if Documents and Media portlet or document_library folders are created and contain uploaded files
Inspect folder permissions for document_library

In the Lifer control panel, go to Documents and Media > select a folder > click the permissions icon. Verify the Guest role or Community Guest permissions do not have View or Access access to sensitive folders

Affected if Guest or unauthenticated users are granted View or Access permissions on document_library folders containing sensitive uploads
Test direct URL access as a guest user

Log out completely, then attempt to access a direct file URL from document_library (format typically: /documents/{folder_id}/{file_id}/{filename}) using an incognito browser window

Affected if The file downloads or displays content without requiring authentication when accessed via direct URL while logged out
Review form submissions that upload to document_library

Check the Forms or Dynamic Data Lists configuration to identify any forms configured to store uploads in document_library, then verify the target folder permissions

Affected if Forms are configured to store uploaded files in document_library folders accessible to guest users

Your environment is affected if you run an affected Lifer Portal or DXP version AND have document_library folders with files accessible to guest users via direct URLs without authentication.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2024.Q1.15 / 2025.Q1.2 or later

Fixed in 2024.Q1.152025.Q1.2

Interim mitigation

Apply the vendor security patches for the affected versions (7.4.0-7.4.3.132 for Portal, and the listed DXP versions). Additionally, review and enforce proper document_library folder permissions to ensure guest users cannot access files they did not upload.

Recommended fix High confidence

LPortal 7.4.3.133+ or DXP 2024.Q1.15+/2024.Q2.14+/2024.Q3.14+/2024.Q4.8+

1. Identify the current LPortal or DXP version by checking the portal-ext.properties or the control panel about page
2. For LPortal 7.4.x users: Upgrade to LPortal 7.4.3.133 or later
3. For DXP 2024.Q1.x users: Upgrade to DXP 2024.Q1.15 or later
4. For DXP 2024.Q2.x users: Upgrade to DXP 2024.Q2.14 or later
5. For DXP 2024.Q3.x users: Upgrade to DXP 2024.Q3.14 or later
6. For DXP 2024.Q4.x users: Upgrade to DXP 2024.Q4.8 or later
7. After upgrade, verify that guest/unauthenticated users can no longer directly access files in document_library via direct URLs

Caveat Standard minor/patch upgrades typically have minimal breaking changes; review Liferays release notes for any deprecation notices

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
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

16.0 hours of engineering $2,840

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-43749 — 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-43749 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-43749?

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.15 / 2025.Q1.2 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.3%

Affects: Digital Experience Platform

Remediation

Need this fixed?

Fix this in Digital Experience Platform 16 hrs · Moderate

Typical engagement from $2,840

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-43749 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