dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-25148

HIGH · 8.1 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to after 7.4.1 or later.
See remediation →
87/100
Remediation priority · High
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
In 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 the `doAsUserId` URL parameter may get leaked when creating linked content using the WYSIWYG editor and while impersonating a user. This may allow remote authenticated users to impersonate a user after accessing the linked content.

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 · moderate confidence

In Liferell Portal and DXP, the WYSIWYG editor leaks the `doAsUserId` URL parameter in generated links when creating linked content while impersonating a user. This allows an authenticated attacker who accesses the leaked link to inherit the impersonated user's session and privileges.

MitigationUpgrade to Liferell Portal 7.4.2+, Liferell DXP 7.3 Service Pack 3+, or Liferell DXP 7.2 Fix Pack 15+ to obtain the patch that prevents the doAsUserId parameter from being exposed in WYSIWYG-generated links.

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
DxpApplication
Affected:= 7.3
Liferay PortalApplication
Affected:>= 7.2.0, <= 7.4.1

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Check Liferell Portal/DXP version
    Access the Liferell Control Panel or check the portal-ext.properties file for the product.version. Alternatively, access /api/jsonws or check the bundle version in the Liferell Marketplace or OSGi console.
    Affected if The installed version is 7.2.0 through 7.4.1, or specifically 7.2, 7.3, or 7.4.x versions within this range
  2. Verify User Impersonation is enabled
    In Liferell Control Panel, go to Control Panel > Users > Users and Roles. Check if the 'Impersonate' option is available for any user, or check portal-ext.properties for 'users.impersonation.enabled=true'
    Affected if User impersonation is enabled and the instance uses the WYSIWYG editor
  3. Inspect WYSIWYG-generated links for doAsUserId leakage
    Create or edit content using the WYSIWYG editor while impersonating another user (via the Impersonate option). Save the content and inspect the generated HTML or rendered page. Look for URLs containing the parameter 'doAsUserId' in hyperlinks, images, or embedded content.
    Affected if Any hyperlink, image link, or embedded URL in the WYSIWYG content contains 'doAsUserId=' followed by a user ID value
  4. Search existing content for leaked doAsUserId parameters
    Use Liferell's search functionality or query the database (Liferell_MESSAGE_BOARDS_MESSAGE, Liferell_JOURNAL_ARTICLE tables) for content containing the string 'doAsUserId=' across all web content, blogs, message board posts, and documents.
    Affected if Any stored content contains URLs with the doAsUserId parameter

A user is affected if their Liferell version is between 7.2.0 and 7.4.1 inclusive, user impersonation is enabled, and WYSIWYG-generated links contain the doAsUserId parameter.

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 a release after 7.4.1
Interim mitigation

Upgrade to Liferell Portal 7.4.2+, Liferell DXP 7.3 Service Pack 3+, or Liferell DXP 7.2 Fix Pack 15+ to obtain the patch that prevents the doAsUserId parameter from being exposed in WYSIWYG-generated links.

Recommended fix High confidence

Lifer DXP 7.3 SP3+ / DXP 7.2 FP15+ / Portal 7.4.2+

  1. For Lifer DXP 7.3: Apply Service Pack 3 or later to remediate the vulnerability
  2. For Lifer DXP 7.2: Apply Fix Pack 15 or later to remediate the vulnerability
  3. For Lifer Portal 7.4: Upgrade to version 7.4.2 or later where the issue is fixed
  4. After applying the patch/upgrade, verify that the doAsUserId parameter is no longer exposed in WYSIWYG editor-generated links
  5. Confirm that user impersonation functions correctly without leaking credentials through URL parameters

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 / 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-25148 — 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-25148 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