dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25144

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to 7.4.3.26 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
The IFrame widget in Liferay Portal 7.2.0 through 7.4.3.26, and older unsupported versions, and Liferay DXP 7.4 before update 27, 7.3 before update 6, 7.2 before fix pack 19, and older unsupported versions does not check the URL of the IFrame, which allows remote authenticated users to cause a denial-of-service (DoS) via a self referencing IFrame.

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 IFrame widget in Lifford Portal and DXP lacks proper URL validation, allowing authenticated users to embed a self-referencing IFrame that points to its own page. This creates an infinite loading loop causing denial of service.

MitigationApply the vendor patches (Lifford Portal 7.4.3.27+, DXP 7.4 update 27+, 7.3 update 6+, 7.2 fix pack 19+) which add URL validation to prevent self-referencing or otherwise dangerous iframe URLs.

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.2
DxpApplication
Affected:= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.2.0, < 7.4.3.26

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. Determine the installed Lifford Portal or DXP version
    Access the Lifford Control Panel, go to Configuration > Server Administration > General, or check the portal-ext.properties file for the version property. Alternatively, access /api/jsonws/invoke?p_p_state=maximized and look for the getVersion API call.
    Affected if The installed version is 7.2, 7.3, 7.4, or any version >= 7.2.0 and < 7.4.3.26.
  2. Confirm the IFrame widget is deployed and available
    Log in as an administrator, navigate to Site Builder > Pages, edit any page, and check the widget palette for the IFrame widget under the Advanced category. Alternatively, search for 'IFrame' in the widget catalog.
    Affected if The IFrame widget appears in the available widget list and can be added to pages by authenticated users.
  3. Identify pages with IFrame widgets configured
    Use the Lifford Search function or query the database (Layout表) for page content containing the IFrame portlet. Inspect the IFrame widget configuration to view the embedded URL.
    Affected if Any page contains an IFrame widget where the Source URL points to the same page hosting the IFrame widget, creating a self-referencing loop.
  4. Test for self-referencing IFrame behavior
    Add an IFrame widget to a page, configure it with the page's own URL as the source (for example, if on /web/guest/page1, set iframe source to /web/guest/page1), and observe if the page enters an infinite loading loop.
    Affected if The page becomes unresponsive or continuously loads without completing, indicating the vulnerability is present.

A user is affected if they are running a Lifford Portal or DXP version within the affected ranges (7.2, 7.3, 7.4, or >= 7.2.0 to < 7.4.3.26) and have the IFrame widget deployed with a self-referencing URL configuration.

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.26 or later
Fixed in 7.4.3.26
Interim mitigation

Apply the vendor patches (Lifford Portal 7.4.3.27+, DXP 7.4 update 27+, 7.3 update 6+, 7.2 fix pack 19+) which add URL validation to prevent self-referencing or otherwise dangerous iframe URLs.

Recommended fix High confidence

Lifer Portal 7.4.3.26+ or DXP fix pack 19+/update 6+/update 27+ depending on version

  1. 1. Identify the exact Lifer installation (Portal or DXP) and current version using the Server Administration panel or bundle version.
  2. 2. For Lifer Portal: upgrade to version 7.4.3.26 or later.
  3. 3. For Lifer DXP 7.2: apply fix pack 19 or later.
  4. 4. For Lifer DXP 7.3: apply update 6 or later.
  5. 5. For Lifer DXP 7.4: apply update 27 or later.
  6. 6. After upgrading, restart the application server and verify the IFrame widget functions correctly.
Caveat Review release notes for your specific upgrade path as there may be breaking changes between major updates; test thoroughly in non-production first

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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