dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-3586

HIGH · 7.2 CVSS v3.1 Published 2025-09-01
Fix available
A fix is available. Upgrade to 7.4.3.43 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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
In Liferay Portal 7.4.3.27 through 7.4.3.42, and Liferay DXP 2024.Q1.1 through 2024.Q1.20, 2023.Q4.0 through 2023.Q4.10, 2023.Q3.1 through 2023.Q3.10, 7.4 update 27 through update 42 (Liferay PaaS, and Liferay Self-Hosted), the Objects module does not restrict the use of Groovy scripts in Object actions for Admin Users. This allows remote authenticated admin users with the Instance Administrator role to execute arbitrary Groovy scripts (i.e., remote code execution) through Object actions. In contrast, in Liferay DXP (Liferay SaaS), the use of Groovy in Object actions is not allowed due to the high security risks it poses. Starting from Liferay DXP 2024.Q2 and later, a new feature has been introduced in Instance Settings that allows administrators to configure whether Groovy scripts are allowed in their instances.

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

The Objects module in Liferay Portal 7.4.3.27-7.4.3.42 and DXP versions 2024.Q1.1-2024.Q1.20, 2023.Q4.0-2023.Q4.10, and 2023.Q3.1-2023.Q3.10 fails to restrict Groovy script execution in Object actions. This allows authenticated Instance Administrators to execute arbitrary Groovy scripts, achieving remote code execution.

MitigationUpgrade to Liferay DXP 2024.Q2 or later and disable Groovy scripts in Instance Settings, or apply available patches to restrict Groovy script execution in Object actions.

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.10>= 2023.q4.0, <= 2023.q4.10>= 2024.Q1.1, <= 2024.Q1.20= 7.4
Liferay PortalApplication
Affected:>= 7.4.3.27, < 7.4.3.43

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Lifer Portal version
    Log into the Control Panel and navigate to Configuration > Instance Settings > General, or check the welcome page footer which displays the Lifer Portal version.
    Affected if The installed version is 7.4.3.27 through 7.4.3.42 (inclusive)
  2. Check Lifer DXP version
    Log into the Control Panel and navigate to Configuration > Instance Settings > General, or check the welcome page footer which displays the Lifer DXP version.
    Affected if The installed version is 2023.Q3.1 through 2023.Q3.10, 2023.Q4.0 through 2023.Q4.10, or 2024.Q1.1 through 2024.Q1.20 (inclusive)
  3. Verify Objects module is present and enabled
    Navigate to Control Panel > Object in the Lifer interface. Confirm that the Objects module is accessible and Object definitions can be created or edited.
    Affected if The Objects module is present and accessible in the Control Panel
  4. Check Groovy script execution in Object actions
    Navigate to Control Panel > Object > select an Object definition > Actions tab. Create or edit an action and verify if a Groovy script option is available in the script editor.
    Affected if Groovy script execution is available as a script option when configuring Object actions

A user is affected if their Lifer Portal is version 7.4.3.27-7.4.3.42 or DXP is version 2023.Q3.1-2023.Q3.10/2023.Q4.0-2023.Q4.10/2024.Q1.1-2024.Q1.20 AND the Objects module with Groovy script support in Object actions is enabled.

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.43 or later
Fixed in 7.4.3.43
Interim mitigation

Upgrade to Liferay DXP 2024.Q2 or later and disable Groovy scripts in Instance Settings, or apply available patches to restrict Groovy script execution in Object actions.

Recommended fix High confidence

Liferay Portal: 7.4.3.43 or later; Liferay DXP: 2024.Q2 or later

  1. 1. Identify the current Liferay product (Portal or DXP) and exact version using the Liferay Control Panel > Configuration > Instance Settings > General > Platform Information.
  2. 2. For Liferay Portal: Upgrade to version 7.4.3.43 or later.
  3. 3. For Liferay DXP: Upgrade to 2024.Q2 or later release to receive the fix and new Instance Settings configuration option.
  4. 4. After upgrading to 2024.Q2 or later, navigate to Control Panel > Instance Settings > Object > Actions.
  5. 5. Configure the 'Allow Groovy Scripts in Object Actions' setting to disabled (recommended) to prevent the vulnerability, unless Groovy scripting is explicitly required for business logic.
Caveat Upgrading across major version quarters (e.g., 2023.Q3 to 2024.Q2) may introduce compatibility changes; review Liferay upgrade notes for deprecations and breaking changes.

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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