Liferay Portal Vulnerable to Cross-Site Scripting in Dynamic Data Mapping

Exploitation

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

CVSS 4.0

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

EPSS

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

A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.132, and Liferay DXP 2025.Q2.0 through 2025.Q2.2, 2025.Q1.0 through 2025.Q1.14, 2024.Q4.0 through 2024.Q4.7, 2024.Q3.0 through 2024.Q3.13, 2024.Q2.0 through 2024.Q2.13, 2024.Q1.1 through 2024.Q1.18 and 7.4 GA through update 92 allows a remote authenticated attacker to inject JavaScript code via comliferaydynamicdatamappingwebportletDDMPortletportletNamespace and comliferaydynamicdatamappingwebportletDDMPortletnamespace parameter.

Published by the source

20 Aug 2025, 21:30 UTC

Last modified by the source

29 Aug 2025, 21:13 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mpww-r37c-vxjw

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

# Patch Next advisory brief: CVE-2025-43746

Advisory: Liferay Portal Vulnerable to Cross-Site Scripting in Dynamic Data Mapping
IDs: CVE-2025-43746, GHSA-mpww-r37c-vxjw
Record: https://patchnext.com/advisories/cve-2025-43746 (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: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: ccom.liferay:com.liferay.dynamic.data.mapping.web 5.0.122. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.portal.bom: affected >= 7.4.0-ga1, <= 7.4.3.132-ga132
- Maven ccom.liferay:com.liferay.dynamic.data.mapping.web: affected < 5.0.122; fixed in 5.0.122

## Suggested inspection (read-only)
- Maven com.liferay.portal:release.portal.bom: check the installed version with your package manager.
- Maven ccom.liferay:com.liferay.dynamic.data.mapping.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.portal.bom, ccom.liferay:com.liferay.dynamic.data.mapping.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-mpww-r37c-vxjw (GitHub-reviewed advisory GHSA-mpww-r37c-vxjw lists affected ranges: Maven com.liferay.portal:release.portal.bom >=7.4.0-ga1 =0 <5.0.122)

Commands are suggestions: review each one before running it.