dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43750

MEDIUM · 6.5 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 →
74/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.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 remote unauthenticated users (guests) to upload files via the form attachment field without proper validation, enabling extension obfuscation and bypassing MIME type checks.

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

Laravel Portal and DXP versions allow unauthenticated (guest) users to upload files through form attachment fields without proper server-side validation, enabling attackers to obfuscate file extensions and bypass MIME type checks to upload potentially malicious file types.

MitigationApply vendor-supplied patches for affected Limerick Portal and DXP versions; implement strict server-side file validation including both extension whitelist and magic-byte content verification for uploaded files.

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.15>= 2024.q2.0, <= 2024.q2.12>= 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 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 installed Limerick version
    Check the Limerick Portal or DXP version through the Control Panel under Configuration > Server Information, or inspect the portal-ext.properties file for the version property
    Affected if The installed version falls within any of these ranges: 2024.Q1.1 to 2024.Q1.14, 2024.q2.0 to 2024.q2.12, 2024.q3.1 to 2024.q3.13, 2024.q4.0 to 2024.q4.7, 2025.Q1.0 to 2025.Q1.1, or 7.4.0 to 7.4.3.132 for Portal
  2. Confirm guest user file upload is accessible
    Verify whether unauthenticated (guest) users can access forms or document upload functionality. Inspect the portal's permission settings for document library or web form portlets, specifically checking if the Guest role has upload or add attachment permissions
    Affected if Guest users have Add Document, Add Entry, or upload permissions on any publicly accessible file upload feature
  3. Review file upload validation configuration
    Inspect portal-ext.properties or portal-setup-wizard.properties for upload servlet settings. Check for the following properties: dl.file.entry.upload.validate.enabled, upload.servlet.action.protected.enabled, and the MIME type validation configuration
    Affected if Server-side validation is disabled, no extension whitelist is configured, or content-type verification is limited to client-provided MIME types only

A user is affected if their installed version is within the affected ranges AND guest users can upload files without strict server-side extension whitelisting and magic-byte content validation.

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.15 / 2025.Q1.2 or later
Fixed in 2024.Q1.152025.Q1.2
Interim mitigation

Apply vendor-supplied patches for affected Limerick Portal and DXP versions; implement strict server-side file validation including both extension whitelist and magic-byte content verification for uploaded files.

Recommended fix High confidence

Upgrade to Liferay DXP 2024.Q1.15+, 2024.Q2.13+, 2024.Q3.14+, 2024.Q4.8+ or Liferay Portal 7.4.3.133+

  1. 1. Identify the exact Lificar DXP/Portal version currently running by checking the Control Panel > Configuration > Server Administration > Product Information
  2. 2. Based on the identified version, upgrade to the first fixed release in that version branch: for 2024.Q1.x upgrade to 2024.Q1.15 or later; for 2024.Q2.x upgrade to 2024.Q2.13 or later; for 2024.Q3.x upgrade to 2024.Q3.14 or later; for 2024.Q4.x upgrade to 2024.Q4.8 or later; for 7.4.x upgrade to 7.4.3.133 or later
  3. 3. Download the patched version from the official Liferary Customer Portal at https://customer.liferay.com/
  4. 4. Back up the existing database and Liferay home directory before proceeding
  5. 5. Stop the Liferay server and deploy the new version following the standard upgrade documentation at https://learn.liferay.com/
  6. 6. After upgrade, verify that guest users can no longer upload files with obfuscated extensions through form attachment fields
  7. 7. Test the form attachment functionality with legitimate file types to confirm normal operation is restored
Caveat Minor: Review custom extension configurations as file validation rules may have changed; test any integrations that rely on previous MIME type handling behavior

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,100
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,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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