Skip to content

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

Critical severity GitHub Reviewed Published Feb 20, 2024 to the GitHub Advisory Database • Updated Dec 11, 2024

Package

maven com.liferay.portal:com.liferay.portal.web (Maven)

Affected versions

< 5.0.96

Patched versions

5.0.96
maven com.liferay.portal:release.dxp.bom (Maven)
>= 7.4.0, < 7.4.13.u9
>= 7.3.0, < 7.3.10.u4
< 7.2.10.fp19
7.4.13.u9
7.3.10.u4
7.2.10.fp19
maven com.liferay.portal:release.portal.bom (Maven)
< 7.4.3.13
7.4.3.13

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.

References

Published by the National Vulnerability Database Feb 20, 2024
Published to the GitHub Advisory Database Feb 20, 2024
Reviewed Dec 11, 2024
Last updated Dec 11, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2024-25610

GHSA ID

GHSA-vvpf-53qx-cxhh

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.