# CVE-2024-38002: Liferay Portal and Liferay DXP Workflow Component Does Not Check User Permissions > Authenticated users can modify workflow definitions via the headless API due to missing permission checks, leading to arbitrary code execution. - **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 22 Oct 2024 - **Updated:** 13 Oct 2025 - **Also known as:** GHSA-3mfq-fp2f-vwqh ## What is CVE-2024-38002? CVE-2024-38002 is a critical missing authorization vulnerability in Liferay Digital Experience Platform, published on 22 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2024-38002? 10 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3.1 | 2023.Q3.9 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3.1 | 2023.Q3.9 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q4.0 | 2023.Q4.6 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q4.0 | 2023.Q4.6 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3-ga | 7.3.10.u36 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.3-ga | 7.3.10.u36 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4-ga | 7.4.13.u92 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4-ga | 7.4.13.u92 | | `com.liferay.portal:release.portal.bom` | Maven | From 7.3.2-ga3 | 7.4.3.112-ga112 | | `com.liferay.portal:release.portal.bom` | Maven | From 7.3.2-ga3 | 7.4.3.112-ga112 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2024-38002? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 2023.Q3.9, 2023.Q4.6, 7.3.10.u36 or 7.4.13.u92. ## Is CVE-2024-38002 being exploited? There is no known exploitation of CVE-2024-38002 in the wild and no public exploit code. ## Other vulnerabilities in Liferay Digital Experience Platform - [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6) - [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6) - [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6) - [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6) - [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-38002 and fix it if it is affected. What it is: CVE-2024-38002 is a critical missing authorization vulnerability in Liferay Digital Experience Platform, published on 22 Oct 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-38002 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3.1; fixed in 2023.Q3.9 - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3.1; fixed in 2023.Q3.9 - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q4.0; fixed in 2023.Q4.6 - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q4.0; fixed in 2023.Q4.6 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3-ga; fixed in 7.3.10.u36 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.3-ga; fixed in 7.3.10.u36 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.4-ga; fixed in 7.4.13.u92 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.4-ga; fixed in 7.4.13.u92 - com.liferay.portal:release.portal.bom (Maven): affected from 7.3.2-ga3; fixed in 7.4.3.112-ga112 - com.liferay.portal:release.portal.bom (Maven): affected from 7.3.2-ga3; fixed in 7.4.3.112-ga112 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-38002/ (Markdown: https://insights.sbomify.com/CVE-2024-38002/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-38002 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-38002 - OSV: https://osv.dev/vulnerability/CVE-2024-38002 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-38002/ Summaries are generated and may contain mistakes; the official description above is the record.