dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43785

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 7.4.3.129 / 2024.Q1.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Stored cross-site scripting (XSS) vulnerability in Liferay Portal 7.4.3.45 through 7.4.3.128, and Liferay DXP 2024 Q2.0 through 2024.Q2.9, 2024.Q1.1 through 2024.Q1.12, and 7.4 update 45 through update 92 allows remote attackers to execute an arbitrary web script or HTML in the My Workflow Tasks page.

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 · moderate confidence

Stored XSS vulnerability in Lifer ay Portal/DXP's My Workflow Tasks page allows authenticated attackers to inject malicious JavaScript/HTML that persists on the server and executes in browsers of other users who view the workflow tasks.

MitigationApply the vendor security patch or upgrade to a Lifer ay version beyond the affected ranges (7.4.3.129+, 2024.Q2.10+, 2024.Q1.13+, or 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:>= 2024.Q1.1, < 2024.Q1.13>= 2024.Q2.0, <= 2024.Q2.9= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.45, < 7.4.3.129

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine Lifer ay Portal/DXP version
    Locate the version file or check the control panel: For Lifer ay Portal, check the OSGi bundle version or the liferay-portal.properties file. For DXP, check the Lifer ay DXP version from the Control Panel > Configuration > Server Administration > Version. Alternatively, check the manifest.mf file in the osgi/core directory or the portal-impl.jar properties.
    Affected if The installed version falls within these ranges: Lifer ay DXP 2024.Q1.1 through 2024.Q1.12, 2024.Q2.0 through 2024.Q2.9, or version 7.4; OR Lifer ay Portal 7.4.3.45 through 7.4.3.128
  2. Confirm My Workflow Tasks feature is accessible
    Navigate to the My Workflow Tasks page in the Lifer ay interface. This is typically found under the User Menu or the Workflow section. Verify that authenticated users can access this page to submit workflow tasks that would contain the malicious payload.
    Affected if The My Workflow Tasks page is accessible to authenticated users in your environment
  3. Verify authentication is enabled for workflow tasks
    Check the workflow configuration in Control Panel > Workflow > Process Builder. Confirm that workflow definitions are active and users can submit or interact with workflow tasks. Also verify that the Lifer ay instance has user accounts and authentication is not disabled.
    Affected if The workflow system is active and users can authenticate to access the My Workflow Tasks functionality

Your environment is affected if you are running a Lifer ay Portal 7.4.3.45-7.4.3.128 or DXP 2024.Q1.1-2024.Q1.12/2024.Q2.0-2024.Q2.9/7.4 version AND the My Workflow Tasks feature is accessible to authenticated users.

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.129 / 2024.Q1.13 or later
Fixed in 7.4.3.1292024.Q1.13
Interim mitigation

Apply the vendor security patch or upgrade to a Lifer ay version beyond the affected ranges (7.4.3.129+, 2024.Q2.10+, 2024.Q1.13+, or update 93+).

Recommended fix High confidence

Lifter Portal 7.4.3.129+ / DXP 2024.Q1.13+ / DXP 2024.Q2.10+ / DXP 7.4 update 93+

  1. 1. Identify the exact Lifting Portal or DXP version currently running by checking the Control Panel > Server Administration > Product Information
  2. 2. For Lifter Portal 7.4.x users: Upgrade to version 7.4.3.129 or later
  3. 3. For Lifer DXP 2024.Q1.x users: Upgrade to version 2024.Q1.13 or later
  4. 4. For Lifer DXP 2024.Q2.x users: Upgrade to version 2024.Q2.10 or later
  5. 5. For Lifer DXP 7.4 (update model) users: Upgrade to update 93 or later
  6. 6. After upgrading, verify the fix by testing the My Workflow Tasks page with malicious input to confirm XSS is no longer exploitable
  7. 7. Clear all caches and re-index search after upgrade to ensure clean state
Caveat Standard upgrade risks apply - test in staging environment first, backup database, review breaking changes in release notes

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43785 — 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-43785 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