dbcve.org
Liferay PortalApplication · Liferay

CVE-2024-25147

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-21
Fix available
A fix is available. Upgrade to 7.2 / 7.4.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting (XSS) vulnerability in HtmlUtil.escapeJsLink 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 allows remote attackers to inject arbitrary web script or HTML via crafted javascript: style links.

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

Cross-site scripting (XSS) vulnerability in Limerick Portal/DXP's HtmlUtil.escapeJsLink function fails to properly sanitize javascript: style links, allowing remote attackers to inject arbitrary web script or HTML that executes in victim browsers.

MitigationUpgrade to Limerick Portal 7.4.2+, DXP 7.3 service pack 3+, or DXP 7.2 fix pack 15+. Alternatively, implement output encoding or input validation on any user-supplied content processed by HtmlUtil.escapeJsLink.

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.2
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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 type
    Check whether your deployment is Liferay Portal or Liferay Digital Experience Platform (DXP). This can be found in the control panel, admin dashboard, or by examining the application WAR/ear file name.
    Affected if The product is Liferay Portal or DXP and the version falls within affected ranges
  2. Determine the installed Liferay version
    Navigate to Control Panel > Configuration > Server Information, or inspect the portal-impl.jar file within the Liferay installation for the version.properties or portal.properties file.
    Affected if The version is Liferay Portal < 7.4.2, or DXP = 7.2, or DXP = 7.3, or DXP < 7.2
  3. Locate usage of HtmlUtil.escapeJsLink
    Search your codebase (including custom portlets, themes, and modules) for calls to HtmlUtil.escapeJsLink or com/liferay/portal/util/HtmlUtil. This method is part of the portal-util.jar.
    Affected if Code references HtmlUtil.escapeJsLink and processes user-supplied content through it
  4. Identify data flow into escapeJsLink
    Review custom portlets, themes, and templates (freemarker, velocity, soy) that invoke HtmlUtil.escapeJsLink on any parameter derived from request parameters, form inputs, or URL parameters.
    Affected if User-controllable input (request params, form fields, URL query strings) is passed to escapeJsLink without prior encoding

Your environment is affected if you run Liferay Portal < 7.4.2 or DXP 7.2/7.3 and your code or customizations use HtmlUtil.escapeJsLink to process user-supplied links.

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 Limerick Portal 7.4.2+, DXP 7.3 service pack 3+, or DXP 7.2 fix pack 15+. Alternatively, implement output encoding or input validation on any user-supplied content processed by HtmlUtil.escapeJsLink.

Recommended fix High confidence

Liferay Portal 7.4.2+ or Liferay DXP 7.3 SP3+ or Liferay DXP 7.2 FP15+

  1. Identify the current Liferay Portal or DXP version in use
  2. If using Liferay Portal 7.2.x or 7.3.x or 7.4.x: upgrade to Liferay Portal version 7.4.2 or later
  3. If using Liferay DXP 7.3.x: apply Service Pack 3 or later
  4. If using Liferay DXP 7.2.x: apply Fix Pack 15 or later
  5. After upgrading, verify that HtmlUtil.escapeJsLink properly sanitizes javascript: style links
  6. Test the fix in a staging environment before deploying to production
Caveat Major version upgrades may require testing custom plugins, themes, and scripts for compatibility; review Liferay upgrade documentation for migration considerations

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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