Skip to content

GHSA-vvpf-53qx-cxhh CVE-2024-25610

Liferay Portal has a Stored XSS with Blog entries (Insecure defaults)

Medium Maven
Severity
9.0 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.52%
Chance of exploitation in the next 30 days. Higher than 44.03% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1188 Initialization of a Resource with an Insecure Default
Fix
Available
3 packages have a fixed version

Description

In Liferay Portal 7.2.0 through 7.4.3.12, and older unsupported versions, and Liferay DXP 7.4 before update 9, 7.3 before update 4, 7.2 before fix pack 19, and older unsupported versions, the default configuration does not sanitize blog entries of JavaScript, which allows remote authenticated users to inject arbitrary web script or HTML (XSS) via a crafted payload injected into a blog entry’s content text field.

Affected versions

Maven

PackageVulnerableFixed in
com.liferay.portal:com.liferay.portal.web
< 5.0.96
5.0.96
com.liferay.portal:release.dxp.bom
>= 7.4.0, < 7.4.13.u9
7.4.13.u9
com.liferay.portal:release.dxp.bom
>= 7.3.0, < 7.3.10.u4
7.3.10.u4
com.liferay.portal:release.dxp.bom
< 7.2.10.fp19
7.2.10.fp19
com.liferay.portal:release.portal.bom
< 7.4.3.13
7.4.3.13

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

com.liferay.portal:com.liferay.portal.web Maven → 5.0.96

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>com.liferay.portal.web</artifactId><version>5.0.96</version></dependency>
gradle
implementation("com.liferay.portal:com.liferay.portal.web:5.0.96")

com.liferay.portal:release.dxp.bom Maven → 7.4.13.u9

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.dxp.bom</artifactId><version>7.4.13.u9</version></dependency>
gradle
implementation("com.liferay.portal:release.dxp.bom:7.4.13.u9")

com.liferay.portal:release.portal.bom Maven → 7.4.3.13

maven
<dependency><groupId>com.liferay.portal</groupId><artifactId>release.portal.bom</artifactId><version>7.4.3.13</version></dependency>
gradle
implementation("com.liferay.portal:release.portal.bom:7.4.3.13")

Severity breakdown

CVSS 3.1 9.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-1188: Initialization of a Resource with an Insecure Default

The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-2j97-4jmq-c4xf
Liferay Portal Vulnerable to Reflected XSS via the selectedLanguageId Parameter
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-56jv-4ww3-65mw
Liferay Portal is vulnerable to XSS in the Blogs widget
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-f5vh-4rj2-w8r8
Liferay Portal is vulnerable to DNS rebinding attacks
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-8hw3-ghwv-crfh
Liferay Portal vulnerable to password enumeration
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gv7w-jh8g-vr73
Liferay Portal Does Not Limit Access to APIs Before Email Verification
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-gh4w-8qgq-8w9r
Liferay Portal Vulnerable to CSRF in Headless APIs
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-xcj6-xpjg-c4xr
Liferay Portal Stores Password Reset Tokens in Plain Text
Medium Also affects com.liferay.portal:release.portal.bom
GHSA-vgqx-447m-wvcj
Liferay Portal Vulnerable to DoS via Crafted Headless API Request
High Also affects com.liferay.portal:release.portal.bom
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor