dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-62239

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-10
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability in workflow process builder in Liferay Portal 7.4.3.21 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 21 through update 92 allows remote authenticated attackers to inject arbitrary web script or HTML via the crafted input in a workflow definition.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in Liferay Portal/DXP workflow process builder allows authenticated attackers to inject arbitrary web script or HTML via crafted input in workflow definitions. The vulnerability exists because user-supplied content in workflow definitions is not properly sanitized before rendering.

MitigationUpgrade to Liferay Portal 7.4.3.112 or later, or apply the relevant LXDXP patches for the supported versions (2023.Q4.6+, 2023.Q3.9+, update 93+).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digital Experience PlatformApplication
Affected:>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.21, < 7.4.3.112

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Lifer Portal/DXP version
    Access the Lifer Control Panel, go to Configuration > Server Administration > Product Information, or check the bundle.properties file for the version property
    Affected if the version falls within 7.4.3.21 through 7.4.3.111 for Lifer Portal, or 2023.q3.1 through 2023.q3.8, 2023.q4.0 through 2023.q4.5, or 7.4 (exact) for DXP
  2. Confirm workflow process builder is accessible
    Log in as an authenticated user and navigate to Control Panel > Workflow > Process Builder, or check if the Kaleo workflow engine is enabled in the Lifer instance
    Affected if authenticated users can access the workflow definition editor or workflow configuration
  3. Check for custom workflow definitions
    Inspect the workflow definitions stored in the database (typically in the KaleoDefinition table) or examine XML definition files deployed in the OSGi module for custom workflows
    Affected if any workflow definitions exist that accept user-supplied input for workflow node names, descriptions, or transition labels
  4. Verify if the workflow designer UI accepts user input
    Use the workflow process builder UI to create or edit a workflow definition and attempt to add a script or description with special characters (less than, greater than, script tags)
    Affected if the input is rendered back without sanitization when the workflow is viewed or executed

A Lifer installation is affected if its version is within the listed ranges AND the workflow process builder feature is accessible to authenticated users who can create or edit workflow definitions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.3.112 / 2023.q3.9 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.q3.92023.q4.6
Interim mitigation

Upgrade to Liferay Portal 7.4.3.112 or later, or apply the relevant LXDXP patches for the supported versions (2023.Q4.6+, 2023.Q3.9+, update 93+).

Recommended fix High confidence

Upgrade to Liferary Portal 7.4.3.112+ or DXP 2023.Q3.9+ / 2023.Q4.6+ / 7.4 update 93+ depending on product line

  1. 1. Identify the currently installed Liferary Portal or DXP version by checking the control panel or the osgi/state directory
  2. 2. For Liferary Portal 7.4.x: Upgrade to version 7.4.3.112 or later
  3. 3. For Liferary DXP 2023.Q3.x: Upgrade to version 2023.q3.9 or later
  4. 4. For Liferary DXP 2023.Q4.x: Upgrade to version 2023.q4.6 or later
  5. 5. For Liferary DXP 7.4 (subscription): Upgrade to update 93 or later
  6. 6. After upgrade, verify the workflow process builder no longer accepts unsanitized script/HTML input in workflow definitions
  7. 7. Test that existing workflow definitions still function correctly after the patch
Caveat Standard upgrade precautions apply - test in non-production environment first, backup database, review deprecation notices

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62239 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62239 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data