dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43758

MEDIUM · 5.3 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2024.Q1.16 / 2025.Q1.6 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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.

NVD · unedited
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 unauthenticated users (guests) to access via URL files uploaded by object entry and stored in document_library

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.

dbcve analysis · high confidence

Lifera Portal and DXP contain an access control bypass where guest/unauthenticated users can directly access files stored in document_library that were uploaded via object entries. This allows unauthorized download of files that should require authenticated access.

MitigationApply the vendor-released patches for the affected versions (7.4.3.132+ or the DXP updates) and verify that unauthenticated access to document_library files is no longer possible.

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

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.

NVD · CPE data
Digital Experience PlatformApplication
Affected:>= 2024.Q1.1, < 2024.Q1.16>= 2024.q2.0, <= 2024.q2.13>= 2024.q3.1, <= 2024.q3.13>= 2024.q4.0, <= 2024.q4.7>= 2025.Q1.0, < 2025.Q1.6= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, <= 7.4.3.132

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.

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? 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.

dbcve checks

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

  1. Identify Lifer Portal/DXP version
    Check the Lifer version by reviewing the Lifer JAR files in the bundle or accessing the Control Panel > Configuration > Server Information in the Lifer UI. Alternatively, check portal-ext.properties or portal-setup-wizard.properties for the version string.
    Affected if The installed version falls within any of the following ranges: >= 2024.Q1.1 and < 2024.Q1.16; >= 2024.q2.0 and <= 2024.q2.13; >= 2024.q3.1 and <= 2024.q3.13; >= 2024.q4.0 and <= 2024.q4.7; >= 2025.Q1.0 and < 2025.Q1.6; = 7.4 (DXP); or >= 7.4.0 and <= 7.4.3.132 (Portal)
  2. Verify Objects module with file upload fields is in use
    Access the Lifer Control Panel > Object Definitions and review custom object definitions. Check if any object definitions include a file field type (typically named 'file' or similar) that stores attachments.
    Affected if Custom object entries with file upload fields exist and have been used to upload documents to the document_library.
  3. Test unauthenticated file access via document_library
    As an unauthenticated (guest) user, attempt to access a file URL that was uploaded through an object entry. The URL typically follows the pattern: /documents/[site-id]/[folder-id]/[file-name] or /c/document_library/get?fileName=[filename]. Use a browser incognito window or curl without authentication headers.
    Affected if The file downloads successfully without requiring login credentials, indicating the access control bypass is present.
  4. Check for recent authentication-required file downloads
    Review server access logs for document_library GET requests. Determine if requests to files uploaded via object entries originate from unauthenticated IP addresses (no session token or LIFERAY_SESSION cookie).
    Affected if Logs show successful GET requests to object-uploaded files from unauthenticated sources.

If the installed Lifer version is within the affected ranges AND files uploaded through object entries are accessible to unauthenticated users, the environment is vulnerable to CVE-2025-43758.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2024.Q1.16 / 2025.Q1.6 or later
Fixed in 2024.Q1.162025.Q1.6
Interim mitigation

Apply the vendor-released patches for the affected versions (7.4.3.132+ or the DXP updates) and verify that unauthenticated access to document_library files is no longer possible.

Recommended fix Moderate confidence

Lifera DXP: upgrade to 2024.Q1.16, 2024.Q2.14, 2024.Q3.14, or 2024.Q4.8 (depending on your release train); Lifer Portal: upgrade to 7.4.3.133 or later

  1. 1. Identify the currently deployed Lifford DXP or Portal version from the admin console or system properties.
  2. 2. Based on the identified version, determine the minimum target fixed version: For DXP 2024.Q1.x, upgrade to 2024.Q1.16 or later; for DXP 2024.Q2.x, upgrade to 2024.Q2.14 or later; for DXP 2024.Q3.x, upgrade to 2024.Q3.14 or later; for DXP 2024.Q4.x, upgrade to 2024.Q4.8 or later; for Liferay Portal 7.4.x, upgrade to 7.4.3.133 or later.
  3. 3. Before upgrading in production, test the new version in a staging environment to verify compatibility with existing customizations and plugins.
  4. 4. Perform a full backup of the database and LIFERAY_HOME directory.
  5. 5. Deploy the upgraded version following the standard Lifer upgrade process.
  6. 6. After upgrade, verify that unauthenticated users can no longer access files in document_library that were uploaded via object entries.
  7. 7. Review other security settings and consider implementing additional access controls on document_library folders.
Caveat Standard Lifer upgrade risks apply - test thoroughly in staging, especially with custom themes/plugins

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43758 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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