Liferay Portal Commerce Shop is vulnerable to Stored XSS through SVG file

Exploitation

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

CVSS 4.0

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

EPSS

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

There is a Stored Cross-Site Scripting (XSS) vulnerability in diagram type products in Commerce in Liferay Portal 7.4.3.18 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.5, 2023.Q3.1 through 2023.Q3.8, and 7.4 update 18 through update 92. This vulnerability allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a SVG file.

Published by the source

8 Oct 2025, 15:32 UTC

Last modified by the source

17 Dec 2025, 00:16 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-893r-jr58-3hxr

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

# Patch Next advisory brief: CVE-2025-43829

Advisory: Liferay Portal Commerce Shop is vulnerable to Stored XSS through SVG file
IDs: CVE-2025-43829, GHSA-893r-jr58-3hxr
Record: https://patchnext.com/advisories/cve-2025-43829 (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: Medium (CVSS 4.8)
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.shop.by.diagram.web 1.0.83. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web: affected >= 1.0.41, < 1.0.83; fixed in 1.0.83

## Suggested inspection (read-only)
- Maven com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web: 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.shop.by.diagram.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-893r-jr58-3hxr (GitHub-reviewed advisory GHSA-893r-jr58-3hxr lists affected ranges: Maven com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web >=1.0.41 <1.0.83)

Commands are suggestions: review each one before running it.