Liferay Portal and DXP allows users to add a note to a different virtual instance

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2025-43810: 0.28% estimated exploitation activity in the next 30 days; percentile 20.25 (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.

Insecure Direct Object Reference (IDOR) vulnerability with commerce order notes in Liferay Portal 7.3.5 through 7.4.3.112, and Liferay DXP 2023.Q4.0 through 2023.Q4.8, 2023.Q3.1 through 2023.Q3.10, and 7.4 GA through update 92 allows remote authenticated users to from one virtual instance to add a note to an order in a different virtual instance via the comliferaycommerceorderwebinternalportletCommerceOrderPortletcommerceOrderId parameter.

Published by the source

23 Sep 2025, 00:32 UTC

Last modified by the source

23 Sep 2025, 15:10 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f372-9rcj-8w2c

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

# Patch Next advisory brief: CVE-2025-43810

Advisory: Liferay Portal and DXP allows users to add a note to a different virtual instance
IDs: CVE-2025-43810, GHSA-f372-9rcj-8w2c
Record: https://patchnext.com/advisories/cve-2025-43810 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay.commerce:com.liferay.commerce.service 11.0.164. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.commerce:com.liferay.commerce.service: affected < 11.0.164; fixed in 11.0.164

## Suggested inspection (read-only)
- Maven com.liferay.commerce:com.liferay.commerce.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.commerce:com.liferay.commerce.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-f372-9rcj-8w2c (GitHub-reviewed advisory GHSA-f372-9rcj-8w2c lists affected ranges: Maven com.liferay.commerce:com.liferay.commerce.service >=0 <11.0.164)

Commands are suggestions: review each one before running it.