dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43752

MEDIUM · 6.5 CVSS v3.1 Published 2025-08-22
Fix available
A fix is available. Upgrade to 2024.Q1.16 / 2025.Q1.5 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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.4, 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 allow users to upload an unlimited amount of files through the object entries attachment fields, the files are stored in the document_library allowing an attacker to cause a potential DDoS.

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

Lifteray Portal and DXP allow users to upload unlimited files through object entry attachment fields, with files stored in document_library. This resource exhaustion vulnerability can be exploited to cause denial of service by filling storage or overwhelming the system.

MitigationImplement file upload limits (size and count) on object entry attachment fields, add rate limiting for upload requests, and enforce proper access controls on document_library storage.

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.10>= 2025.Q1.0, < 2025.Q1.5= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 Liferaya product and version
    Access the Liferaya Control Panel or check the product bundle for the exact version number (typically found in portal-impl/build.properties or via the Gogo shell command 'ver' or through the Control Panel > Configuration > Server Information)
    Affected if The installed version falls within any of these ranges: 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.10, 2025.Q1.0 to 2025.Q1.4, 7.4.0 to 7.4.3.132, or equals 7.4 (for DXP)
  2. Verify if object entry attachment fields are in use
    Navigate to Control Panel > Object > Objects and review any object definitions that contain attachment fields, or query the ObjectDefinition table in the database for fields where 'type' = 'Attachment'
    Affected if Any custom or out-of-the-box object definitions include attachment-type fields that are active in the system
  3. Check file upload limits on attachment fields
    Inspect each object entry definition with attachment fields, look for 'maximum size' and 'maximum number of files' settings in the field configuration panel under Control Panel > Object > Objects > [Object Name] > Fields > [Attachment Field]
    Affected if The attachment field configuration shows no maximum size limit or allows unlimited files (maximum count not set or set to unlimited)
  4. Inspect document_library storage limits
    Check the document_library configuration in portal-ext.properties or via Control Panel > Content > Document Library > Configuration, looking for dl.file.max.size, dl.file.max.count, or storage quota settings
    Affected if No global file size limits, file count limits, or storage quotas are configured for the document library
  5. Check for rate limiting on upload endpoints
    Review any custom or third-party firewall/WAF configurations in front of Liferaya, or check portal.properties for custom upload rate limiting settings
    Affected if No rate limiting is enforced on upload requests (POST to /o/c/object_entries or related attachment upload endpoints)

A system is affected if it runs any of the listed Liferaya versions AND has object entry attachment fields configured without upload limits or rate limiting, allowing unlimited file uploads to document_library storage.

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.5 or later
Fixed in 2024.Q1.162025.Q1.5
Interim mitigation

Implement file upload limits (size and count) on object entry attachment fields, add rate limiting for upload requests, and enforce proper access controls on document_library storage.

Recommended fix Moderate confidence

L Portal 7.4.3.133+ or DXP 2024.Q1.16+ (and subsequent quarterly patches for other affected releases)

  1. 1. Identify the current Liferay installation version (Portal or DXP)
  2. 2. For Liferay Portal 7.4.x: upgrade to version 7.4.3.133 or later
  3. 3. For Lifer Digital Experience Platform 2024.Q1.x: upgrade to 2024.Q1.16 or later
  4. 4. For DXP 2024.Q2.x: upgrade to 2024.Q2.14 or later if available, or the next available quarterly patch
  5. 5. For DXP 2024.Q3.x: upgrade to 2024.Q3.14 or later if available, or the next available quarterly patch
  6. 6. For DXP 2024.Q4.x: upgrade to 2024.Q4.11 or later if available, or the next available quarterly patch
  7. 7. Verify the upgrade by checking the Liferays release notes for CVE-2025-43752
  8. 8. Test the object entry attachment functionality to confirm the fix is applied
Caveat Review Liferays upgrade documentation for any configuration or compatibility changes between versions

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43752 — 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-43752 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