Liferay Portal and Liferay DXP Vulnerable to XSS in the Commerce Module

Exploitation

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

CVSS

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

EPSS

• CVE-2023-42627: 2.79% estimated exploitation activity in the next 30 days; percentile 86.42 (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.

Multiple stored cross-site scripting (XSS) vulnerabilities in the Commerce module before 4.0.35 from Liferay Portal (7.3.5 through 7.4.3.91), and Liferay DXP 7.3 update 33 and earlier, and 7.4 before update 92 allow remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a (1) Shipping Name, (2) Shipping Phone Number, (3) Shipping Address, (4) Shipping Address 2, (5) Shipping Address 3, (6) Shipping Zip, (7) Shipping City, (8) Shipping Region (9), Shipping Country, (10) Billing Name, (11) Billing Phone Number, (12) Billing Address, (13) Billing Address 2, (14) Billing Address 3, (15) Billing Zip, (16) Billing City, (17) Billing Region, (18) Billing Country, or (19) Region Code.

Published by the source

17 Oct 2023, 15:30 UTC

Last modified by the source

29 Jul 2025, 12:22 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-qp68-5v39-r869

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

# Patch Next advisory brief: CVE-2023-42627

Advisory: Liferay Portal and Liferay DXP Vulnerable to XSS in the Commerce Module
IDs: CVE-2023-42627, GHSA-qp68-5v39-r869
Record: https://patchnext.com/advisories/cve-2023-42627 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: com.liferay.commerce:com.liferay.commerce.address.content.web 4.0.35. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.dxp.bom: affected >= 7.3.0, <= 7.3.10.u33; >= 7.4.0, <= 7.4.13.u92
- Maven com.liferay.commerce:com.liferay.commerce.address.content.web: affected < 4.0.35; fixed in 4.0.35

## Suggested inspection (read-only)
- Maven com.liferay.portal:release.dxp.bom: check the installed version with your package manager.
- Maven com.liferay.commerce:com.liferay.commerce.address.content.web: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.dxp.bom, com.liferay.commerce:com.liferay.commerce.address.content.web.
- 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-qp68-5v39-r869 (GitHub-reviewed advisory GHSA-qp68-5v39-r869 lists affected ranges: Maven com.liferay.commerce:com.liferay.commerce.address.content.web >=0 =7.3.0 =7.4.0 <=7.4.13.u92)

Commands are suggestions: review each one before running it.