dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25149

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 7.2 / 7.4.2 or later.
See remediation →
60/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.1, 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 properly restrict membership of a child site when the "Limit membership to members of the parent site" option is enabled, which allows remote authenticated users to add users who are not a member of the parent site to a child site. The added user may obtain permission to perform unauthorized actions in the child site.

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

Lifter Portal and DXP contain an authorization bypass in site membership logic. When the 'Limit membership to members of the parent site' option is enabled for a child site, the application fails to properly validate that added users are actually members of the parent site, allowing authenticated attackers to add arbitrary users to child sites and potentially escalate privileges.

MitigationUpgrade to Lifer Portal 7.4.2 or later, or apply Lifer DXP 7.3 service pack 3 / 7.2 fix pack 15 or later. Alternatively, audit existing child site memberships and remove unauthorized members.

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
Liferay PortalApplication
Affected:< 7.4.2

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Determine installed Lifer Portal or DXP version
    Locate the version information in the Lifer installation. Common locations: the portal-ext.properties file, the Lifer Database (version table in the release_ table), or the OSGi bundle information via the Gogo shell command 'lb | grep liferay'. Compare against the affected ranges: DXP versions 7.2, 7.3 (any patch level) and Portal versions before 7.4.2.
    Affected if The installed version falls within 7.2, 7.3, or any version before 7.4.2 for Portal.
  2. Identify child sites with parent site membership restriction enabled
    Query the Lifer database for sites where the setting 'limitMembershipToParentSiteMembers' is true, or use the Lifer UI: go to Site Administration > Sites, select each child site, navigate to Membership > Site Membership Settings, and check if 'Limit membership to members of the parent site' is toggled on.
    Affected if Any child site has the 'Limit membership to members of the parent site' option enabled.
  3. Audit members of restricted child sites against parent site membership
    For each child site with the restriction enabled, retrieve the list of members via Site Administration > Membership > Site Members. Then retrieve the members of the parent site. Compare the two lists to identify any users present in the child site who are NOT present in the parent site.
    Affected if A child site has members that are not also members of its parent site, indicating the authorization bypass was exploited.

You are affected if your Lifer Portal/DXP version is 7.2, 7.3, or any version before 7.4.2 AND you have child sites with the parent site membership restriction enabled that contain unauthorized members.

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

Upgrade to Lifer Portal 7.4.2 or later, or apply Lifer DXP 7.3 service pack 3 / 7.2 fix pack 15 or later. Alternatively, audit existing child site memberships and remove unauthorized members.

Recommended fix High confidence

L Portal 7.4.2+ / DXP 7.2 Fix Pack 15+ / DXP 7.3 Service Pack 3+

  1. 1. Identify the current L Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Version
  2. 2. For L Portal 7.2.x through 7.4.1: upgrade to L Portal 7.4.2 or later
  3. 3. For DXP 7.2.x: apply Fix Pack 15 or later
  4. 4. For DXP 7.3.x: apply Service Pack 3 or later
  5. 5. After upgrading, verify the "Limit membership to members of the parent site" option works correctly in Site Settings > Membership Policy > Site Members
  6. 6. Test adding a user who is NOT a member of the parent site to confirm the vulnerability is remediated
Caveat Major version upgrades may require compatibility testing with custom plugins/themes; fix packs and service packs are typically low-risk

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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