dbcve.org
Liferay PortalApplication · Liferay

CVE-2024-25151

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 7.2 / 7.4.3.4 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 Calendar module in Liferay Portal 7.2.0 through 7.4.2, and older unsupported versions, and Liferay DXP 7.3 before service pack 3, 7.2 before fix pack 15, and older unsupported versions does not escape user supplied data in the default notification email template, which allows remote authenticated users to inject arbitrary web script or HTML via the title of a calendar event or the user's name. This may lead to a content spoofing or cross-site scripting (XSS) attacks depending on the capability of the receiver's mail client.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in LPortal/L DXP's Calendar module. The default notification email template fails to escape user-supplied data (calendar event titles or user names) before including them in outgoing email notifications. A remote authenticated attacker can inject arbitrary HTML or JavaScript into these fields, which executes when recipients view the malicious emails in vulnerable mail clients.

MitigationUpgrade to LPortal 7.4.3+, L DXP 7.3 service pack 3+, or L DXP 7.2 fix pack 15+. Alternatively, customize the notification email template to properly escape user-supplied input before rendering.

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
Liferay PortalApplication
Affected:>= 7.2.0, < 7.4.3.4
Digital Experience PlatformApplication
Affected:< 7.2= 7.2= 7.3

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. Check the installed LPortal or L DXP version
    Log into the Control Panel and navigate to Configuration > Server Administration > Product Information, or inspect the portal WAR file's manifest. Alternatively, query the OSGi console with 'lb | grep com.liferays.portal'
    Affected if The version is >= 7.2.0 and < 7.4.3.4 for LPortal, or version 7.2.x or 7.3.x for L DXP
  2. Confirm the Calendar module is active
    Navigate to Control Panel > Apps > App Manager, or query the OSGi console with 'lb | grep com.liferays.portal.calendar'. Verify the Calendar bundle is in the Active state
    Affected if The Calendar module is installed and active in the environment
  3. Inspect the default Calendar notification email template
    Navigate to Control Panel > Configuration > Email Templates or Calendar > Configuration > Email Templates. Look for templates related to event notifications (eventAdded, eventUpdated, etc.)
    Affected if Default email templates are in use and contain unescaped placeholders like ${eventTitle} or ${userName} in the HTML body without proper encoding functions (such as htmlEscape or equivalent)
  4. Verify if custom email templates have been applied
    Review the Calendar module email template configuration in the control panel. Check if templates have been customized from the defaults
    Affected if Default templates remain unchanged and no custom escaping has been applied to user-supplied input in the template variables

A user is affected if they run a vulnerable LPortal (7.2.0 to <7.4.3.4) or L DXP (7.2.x or 7.3.x) version with the Calendar module enabled using the default unpatched email notification templates that fail to escape calendar event titles or user names.

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.4 or later
Fixed in 7.27.4.3.4
Interim mitigation

Upgrade to LPortal 7.4.3+, L DXP 7.3 service pack 3+, or L DXP 7.2 fix pack 15+. Alternatively, customize the notification email template to properly escape user-supplied input before rendering.

Recommended fix High confidence

Lifer Portal 7.4.3.4+ / DXP 7.3 Service Pack 3+ / DXP 7.2 Fix Pack 15+

  1. 1. Identify your current Lifer Portal or DXP version by checking the Lifer Control Panel > Configuration > Server Administration.
  2. 2. For Lifer Portal users: Upgrade to version 7.4.3.4 or later to resolve the XSS vulnerability in the Calendar module's notification email template.
  3. 3. For Lifer DXP 7.3 users: Apply Service Pack 3 or later.
  4. 4. For Lifer DXP 7.2 users: Apply Fix Pack 15 or later.
  5. 5. After upgrading, verify the Calendar module notification emails properly escape special characters in event titles and user names by testing with a calendar event containing HTML-like input (e.g., <script>alert(1)</script>) in the title.
Caveat Review custom Calendar notification email templates for compatibility with the escaping changes; any custom templates using raw user input may need adjustment.

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

Fix this in Liferay Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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