dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43824

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-06
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Profile widget in Liferay Portal 7.4.0 through 7.4.3.111, and older unsupported versions, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92, and older unsupported versions uses a user’s name in the “Content-Disposition” header, which allows remote authenticated users to change the file extension when a vCard file is downloaded.

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 · moderate confidence

The Profile widget in Lifteray Portal and DXP uses a user's display name directly in the Content-Disposition header when downloading vCard files. An authenticated attacker can manipulate their profile name to inject a different file extension into the header, potentially causing the browser to misinterpret the file type or enabling social engineering attacks.

MitigationSanitize the filename in the Content-Disposition header by using a fixed or safely generated filename rather than the user's display name, and ensure the extension is always .vcf regardless of user input.

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:<= 7.4>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6
Liferay PortalApplication
Affected:< 7.4.3.112

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 Liferay version
    Access the Liferay Control Panel or check the bundle version information (typically available in the Liferay Dashboard or via the /c/portal/version endpoint)
    Affected if version is less than 7.4.3.112 for Liferay Portal, or is 7.4 or lower, or falls between 2023.q3.1 and 2023.q3.9, or falls between 2023.q4.0 and 2023.q4.6 for DXP
  2. Confirm Profile widget is in use
    Check if the Profile widget/component is enabled on any page within the Liferay instance. This can be verified through the Page Builder or Widget configuration in the Liferay UI.
    Affected if the Profile widget is present and accessible to authenticated users on any site or page
  3. Verify vCard download functionality
    Locate the Profile widget and attempt to access the vCard export/download option. This is typically found within the Profile widget's user settings or account information section.
    Affected if the vCard download/export feature is available and accessible to authenticated users
  4. Confirm authenticated user access
    Verify that standard authenticated users (not just administrators) have the ability to modify their display name and access the Profile widget's vCard download feature.
    Affected if authenticated users can modify their display name and download vCards from the Profile widget

The environment is affected if the Liferay version falls within the affected ranges AND the Profile widget with vCard download is enabled for authenticated users.

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 7.4.3.112 / 2023.q3.9 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.q3.92023.q4.6
Interim mitigation

Sanitize the filename in the Content-Disposition header by using a fixed or safely generated filename rather than the user's display name, and ensure the extension is always .vcf regardless of user input.

Recommended fix High confidence

Liferay Portal 7.4.3.112+ / DXP 2023.Q3.9+ / DXP 2023.Q4.6+

  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.112 or later
  3. 3. For Liferay DXP 2023.Q3.x: Upgrade to version 2023.Q3.9 or later
  4. 4. For Liferay DXP 2023.Q4.x: Upgrade to version 2023.Q4.6 or later
  5. 5. For Liferay DXP 7.4 GA: Upgrade to update 93 or later (or the latest 7.4.x stable release)
  6. 6. After upgrade, verify the Profile widget vCard download functionality works correctly
  7. 7. Test that the Content-Disposition header properly handles special characters in user names
Caveat Standard upgrade risks apply - review customizations and ensure compatibility with the target version before deploying to production

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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