dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25604

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 7.2 / 7.4.3.5 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
Liferay Portal 7.2.0 through 7.4.3.4, and older unsupported versions, and Liferay DXP 7.4.13, 7.3 before service pack 3, 7.2 before fix pack 17, and older unsupported versions does not properly check user permissions, which allows remote authenticated users with the VIEW user permission to edit their own permission via the User and Organizations section of the Control Panel.

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 an Insecure Direct Object Reference (IDOR) / broken access control vulnerability in Liferay Portal and DXP where authenticated users with only VIEW permission can edit their own permissions via the User and Organizations section in the Control Panel, bypassing the intended permission model.

MitigationApply Liferay's official security patches for the affected versions (7.2 fix pack 17+, 7.3 service pack 3+, 7.4.13+, or 7.4.3.5+) to enforce proper permission checks on permission modification actions.

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= 7.3= 7.4
Liferay PortalApplication
Affected:< 7.4.3.5

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 installed Lifer Portal or DXP version
    Check the Lifer version by navigating to Control Panel > Configuration > Server Administration > Product Information, or inspect the portal-ext.properties file for the version property
    Affected if The installed version is Lifer DXP < 7.2, = 7.2, = 7.3, = 7.4, or Lifer Portal < 7.4.3.5
  2. Verify the Control Panel User and Organizations access
    Log in as an authenticated user with only VIEW permission on Users and Organizations, then navigate to Control Panel > Users and Organizations
    Affected if The user can access the User and Organizations section in the Control Panel with only VIEW permission granted
  3. Test permission modification capability
    As a VIEW-only user in the User and Organizations section, attempt to modify permissions (such as adding or removing roles) on a user account they have access to
    Affected if The user can successfully edit or modify permissions when they should only have VIEW permission according to the permission model

A user is affected if the installed Lifer version falls within the affected ranges AND an authenticated user with only VIEW permission can successfully modify permissions in the Control Panel User and Organizations section.

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.5 or later
Fixed in 7.27.4.3.5
Interim mitigation

Apply Liferay's official security patches for the affected versions (7.2 fix pack 17+, 7.3 service pack 3+, 7.4.13+, or 7.4.3.5+) to enforce proper permission checks on permission modification actions.

Recommended fix High confidence

Liferify Portal 7.4.3.5+ / DXP 7.4.13.13+ / DXP 7.3 SP3+ / DXP 7.2 FP17+

  1. 1. Identify the exact Liferify Portal or DXP version currently installed by checking the control panel or server diagnostics
  2. 2. For Liferify Portal: Upgrade to version 7.4.3.5 or later
  3. 3. For Liferify DXP 7.4: Upgrade to version 7.4.13.13 or later (which includes the fix for 7.4.13)
  4. 4. For Liferify DXP 7.3: Apply Service Pack 3 or later
  5. 5. For Liferify DXP 7.2: Apply Fix Pack 17 or later
  6. 6. After upgrade, verify that users with VIEW permission can no longer edit their own permissions in the User and Organizations section
  7. 7. Test that normal permission workflows continue to function correctly
Caveat Review custom permissions configurations after upgrade as behavior changes may affect existing workflows

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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