dbcve.org
Liferay PortalApplication · Liferay

CVE-2024-25602

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
Stored cross-site scripting (XSS) vulnerability in Users Admin module's edit user page 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 17, and older unsupported versions allows remote authenticated users to inject arbitrary web script or HTML via a crafted payload injected into an organization’s “Name” text field

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 cross-site scripting (XSS) vulnerability in Liferay Portal and DXP's Users Admin module allows authenticated users to inject arbitrary web script or HTML via a crafted payload in the organization's 'Name' field during user edit operations.

MitigationApply vendor patches: Liferay Portal 7.4.3 or later, DXP 7.2 fix pack 17+, DXP 7.3 service pack 3+. Additionally, implement input validation and output encoding for organization name fields as a defense-in-depth measure.

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.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. Identify the Liferay product and version
    Check the portal's version information, typically found in the Control Panel under Server Information, or by locating the portal-ext.properties file and checking the version properties. Alternatively, examine the WAR file or Docker image tags if deployed in containers.
    Affected if The installed version is Liferay Portal < 7.4.3.4, or DXP version = 7.2, = 7.3, or < 7.2 (any version before 7.2 is also affected)
  2. Confirm Users Admin module is accessible
    Log into the Liferay portal as an authenticated user with permissions to access the Control Panel. Navigate to Control Panel > Users and verify the Users and Organizations administrative interfaces are available.
    Affected if The Users Admin module is accessible to the authenticated user performing the check
  3. Verify organization management capability
    In the Control Panel, navigate to Users > Organizations. Attempt to view or edit an existing organization, or create a new one. The vulnerability manifests when editing an organization's 'Name' field during user edit operations.
    Affected if The authenticated user has permission to edit organization names through the Users Admin interface

A user is affected if they are running a vulnerable Liferay Portal or DXP version AND have authenticated users with organization edit permissions, as the XSS payload stored in the organization Name field will execute when viewed.

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

Apply vendor patches: Liferay Portal 7.4.3 or later, DXP 7.2 fix pack 17+, DXP 7.3 service pack 3+. Additionally, implement input validation and output encoding for organization name fields as a defense-in-depth measure.

Recommended fix High confidence

LIFERAY PORTAL 7.4.3.4+ | DXP 7.3 SP3+ | DXP 7.2 FP17+

  1. 1. Back up your LIFERAY_HOME directory and database before proceeding with the upgrade
  2. 2. For LIFERAY PORTAL: Upgrade to version 7.4.3.4 or later
  3. 3. For LIFERAY DXP 7.3: Upgrade to Service Pack 3 or later
  4. 4. For LIFERAY DXP 7.2: Upgrade to Fix Pack 17 or later
  5. 5. After upgrade, verify the organization's Name field now properly sanitizes input
  6. 6. Test the Users Admin module's edit user page to confirm the XSS vulnerability is remediated
Caveat Review LIFERAY's official upgrade notes for your version branch for potential breaking changes and deprecation notices

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
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,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 $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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