Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-3mfq-fp2f-vwqh

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

CVSS 9.3 CriticalCriticalEPSS 0.0063 · 50th percentile

Critical, because:

  • CVSS score 9.3: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 22 Oct 2024, 18:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
com.liferay.portal:release.portal.bomMaven>=7.3.2-ga3, <7.4.3.112-ga1127.4.3.112-ga112
com.liferay.portal:release.dxp.bomMaven>=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.u922023.Q4.6, 2023.Q3.9, 7.3.10.u36, 7.4.13.u92
Identifiers
GHSA-3mfq-fp2f-vwqh · CVE-2024-38002
Weakness (CWE)
CWE-862 · CWE-863
Tags
Published
22 Oct 2024
Updated
10 Sept 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

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 do not properly check user permissions when updating a workflow definition. A remote authenticated user can exploit this through the headless API to modify workflow definitions and execute arbitrary code. Upgrade Liferay Portal to 7.4.3.112-ga112 and Liferay DXP to 2023.Q4.6, 2023.Q3.9, 7.3.10.u36, or 7.4.13.u92, depending on the release line in use.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.3 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L CNA (Liferay)
  • CISA KEV Not listed.
  • EPSS 0.0063, the 50th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 22 Oct 2024, 15:12 UTC Confirmed by the CVE List
  2. 22 Oct 2024, 15:15 UTC Confirmed by NVD
  3. 31 Oct 2026, 15:10 UTC First seen by agentprime
  4. 31 Oct 2026, 15:10 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.