Skip to content

Liferay Portal and Liferay DXP Workflow Component Does Not Check User Permissions

Critical severity GitHub Reviewed Published Oct 22, 2024 to the GitHub Advisory Database • Updated Sep 10, 2025

Package

maven com.liferay.portal:release.dxp.bom (Maven)

Affected versions

>= 2023.Q4.0, < 2023.Q4.6
>= 2023.Q3.1, < 2023.Q3.9
>= 7.3-ga, < 7.3.10.u36
>= 7.4-ga, < 7.4.13.u92

Patched versions

2023.Q4.6
2023.Q3.9
7.3.10.u36
7.4.13.u92
maven com.liferay.portal:release.portal.bom (Maven)
>= 7.3.2-ga3, < 7.4.3.112-ga112
7.4.3.112-ga112

Description

The workflow component in Liferay Portal 7.3.2 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, 7.4 GA through update 92 and 7.3 GA through update 36 does not properly check user permissions before updating a workflow definition, which allows remote authenticated users to modify workflow definitions and execute arbitrary code (RCE) via the headless API.

References

Published by the National Vulnerability Database Oct 22, 2024
Published to the GitHub Advisory Database Oct 22, 2024
Reviewed Aug 8, 2025
Last updated Sep 10, 2025

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

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(75th percentile)

Weaknesses

Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Learn more on MITRE.

CVE ID

CVE-2024-38002

GHSA ID

GHSA-3mfq-fp2f-vwqh

Source code

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