Liferay Portal and DXP Instance Admin can execute code using Objects Actions and Validations

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.5 · CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-3586: 0.42% estimated exploitation activity in the next 30 days; percentile 36.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

12 Dec 2025, 21:31 UTC

Last modified by the source

12 Dec 2025, 22:12 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5gv-vj3f-6v2p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-3586

Advisory: Liferay Portal and DXP Instance Admin can execute code using Objects Actions and Validations
IDs: CVE-2025-3586, GHSA-m5gv-vj3f-6v2p
Record: https://patchnext.com/advisories/cve-2025-3586 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay:com.liferay.object.service 1.0.96. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay:com.liferay.object.service: affected < 1.0.96; fixed in 1.0.96

## Suggested inspection (read-only)
- Maven com.liferay:com.liferay.object.service: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay:com.liferay.object.service.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m5gv-vj3f-6v2p (GitHub-reviewed advisory GHSA-m5gv-vj3f-6v2p lists affected ranges: Maven com.liferay:com.liferay.object.service >=0 <1.0.96)

Commands are suggestions: review each one before running it.