dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25145

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-07
Fix available
A fix is available. Upgrade to 7.2 / 7.4.3.12 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
Stored cross-site scripting (XSS) vulnerability in the Portal Search module's Search Result app in Liferay Portal 7.2.0 through 7.4.3.11, and older unsupported versions, and Liferay DXP 7.4 before update 8, 7.3 before update 4, 7.2 before fix pack 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML into the Search Result app's search result if highlighting is disabled by adding any searchable content (e.g., blog, message board message, web content article) to the application.

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

Stored cross-site scripting (XSS) vulnerability in Lifer Portal/DXP's Portal Search module allows authenticated users to inject malicious web scripts into searchable content (blogs, message board messages, web content articles) when the highlighting feature is disabled. The injected script executes in the Search Result app when users view search results.

MitigationUpgrade to Lifer Portal 7.4.3.12+, Lifer DXP 7.4 update 8+, 7.3 update 4+, or 7.2 fix pack 17+. Alternatively, ensure highlighting is enabled as a workaround.

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= 7.2
DxpApplication
Affected:= 7.3= 7.4
Liferay PortalApplication
Affected:<= 7.2.1>= 7.3.0, <= 7.3.7>= 7.4.0, < 7.4.3.12

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 your Lifer Portal/DXP version
    Check the installed Lifer Portal or DXP version in your environment (typically available in the control panel, server info, or deployment manifests)
    Affected if The installed version falls within: Lifer DXP 7.2 (any fix pack before 17), 7.3 (versions up to and including update 3), 7.4 (versions before 7.4.3.12), or Lifer Portal <= 7.2.1, 7.3.0-7.3.7, or 7.4.0-7.4.3.11
  2. Check if Portal Search highlighting is disabled
    Inspect the Search configuration settings in the Portal Search module or control panel to determine whether the highlighting feature is enabled or disabled
    Affected if The highlighting feature is explicitly disabled in your Search configuration
  3. Verify searchable content types are accessible
    Confirm whether your instance has blogs, message board messages, or web content articles modules enabled and accessible to authenticated users
    Affected if Any of these content types (blogs, message boards, web content) are available and searchable in your environment
  4. Confirm Search Result widget is in use
    Check if the Search Result app or portlet is deployed and actively used to display search results to users
    Affected if The Search Result widget is configured to display search results to end users

You are affected if your Lifer version is in the affected range AND the highlighting feature is disabled, allowing authenticated users to inject scripts into searchable content that will execute when others view search results.

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.2 / 7.4.3.12 or later
Fixed in 7.27.4.3.12
Interim mitigation

Upgrade to Lifer Portal 7.4.3.12+, Lifer DXP 7.4 update 8+, 7.3 update 4+, or 7.2 fix pack 17+. Alternatively, ensure highlighting is enabled as a workaround.

Recommended fix High confidence

LPortal 7.4.3.12+ / DXP 7.4 update 8+ / DXP 7.3 update 4+ / DXP 7.2 fix pack 17+

  1. For Liferay Portal 7.2.x users: Apply Liferay Portal 7.2 fix pack 17 or later
  2. For LPortal 7.3.x users: Upgrade to LPortal 7.3.7 and apply update 4 (or later), or migrate to a supported version
  3. For LPortal 7.4.x users: Upgrade to LPortal 7.4.3.12 or later
  4. For Lifer DXP 7.2 users: Apply DXP fix pack 17 or later
  5. For Lifer DXP 7.3 users: Apply DXP 7.3 update 4 or later
  6. For Lifer DXP 7.4 users: Apply DXP 7.4 update 8 or later

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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