dbcve.org
Liferay PortalApplication · Liferay

CVE-2024-26266

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 7.2 / 7.4.3.14 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
Multiple stored cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.2.0 through 7.4.3.13, and older unsupported versions, and Liferay DXP 7.4 before update 10, 7.3 before update 4, 7.2 before fix pack 17, and older unsupported versions allow remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into the first/middle/last name text field of the user who creates an entry in the (1) Announcement widget, or (2) Alerts widget.

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

Stored XSS vulnerability in Limerick Portal/DXP allows authenticated users to inject malicious JavaScript/HTML through the first/middle/last name text field when creating entries in the Announcement or Alerts widgets. The injected payload persists and executes when other users view the content.

MitigationUpgrade to Limerick Portal 7.4.3.14+, Limerick DXP 7.4 update 10+, 7.3 update 4+, or 7.2 fix pack 17+. Alternatively, implement strict input validation and output encoding for user name fields in affected widgets.

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.14
Digital Experience PlatformApplication
Affected:< 7.2= 7.2= 7.3= 7.4

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 installed L Portal/DXP version
    Check the version through the L Portal control panel (Control Panel > Configuration > Server Information) or examine the portal-ext.properties file, or check the OSGi bundle version in the L Portal Karaf console
    Affected if The version falls within the ranges: L Portal >= 7.2.0 and < 7.4.3.14, or DXP versions 7.2, 7.3, or 7.4 (any sub-version)
  2. Determine if Announcement widget is active
    Check if the Announcements portlet/widget is deployed or used in any site page. Navigate to the Control Panel > Apps > Widgets and look for 'Announcements' in the list of available widgets
    Affected if The Announcements widget is available or deployed on the portal
  3. Determine if Alerts widget is active
    Check if the Alerts portlet/widget is deployed or used in any site page. Navigate to the Control Panel > Apps > Widgets and look for 'Alerts' in the list of available widgets
    Affected if The Alerts widget is available or deployed on the portal
  4. Check user account creation/modification permissions
    Verify if authenticated users have permission to create or edit entries in the Announcement or Alerts widgets. Navigate to Control Panel > Users > Roles and check if standard users have access to the Announcements or Alerts portlet
    Affected if Authenticated users (non-admin) can create or edit entries in either widget
  5. Test for XSS in name fields
    Create or edit an Announcement/Alert entry and inject a test XSS payload (e.g., <script>alert(1)</script> or <img src=x onerror=alert(1)> in the first, middle, or last name field when entering the creator's name. Then view the entry as a different user
    Affected if The payload executes or renders as raw HTML when the entry is viewed by other users, confirming stored XSS

Your environment is affected if you run a vulnerable L Portal/DXP version AND have the Announcements or Alerts widgets accessible to authenticated users who can inject script content through name fields that persist and execute for other users viewing the content.

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.14 or later
Fixed in 7.27.4.3.14
Interim mitigation

Upgrade to Limerick Portal 7.4.3.14+, Limerick DXP 7.4 update 10+, 7.3 update 4+, or 7.2 fix pack 17+. Alternatively, implement strict input validation and output encoding for user name fields in affected widgets.

Recommended fix High confidence

Limerick Portal 7.4.3.14; DXP 7.4 update 10; DXP 7.3 update 4; DXP 7.2 fix pack 17

  1. 1. Identify the current Limerick Portal or DXP version in use by checking the Control Panel > Configuration > Server Administration > Index
Caveat Review Limerick's upgrade documentation for any breaking changes between current and target version, especially when crossing major version boundaries

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

Fix this in Liferay Portal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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