CVE-2025-43829 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web. A fix is available for com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web — see the affected versions and patch details below.
Liferay Portal Commerce Shop is vulnerable to Stored XSS through SVG file
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-43829.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.liferay.commerce:com.liferay.commerce.shop.by.diagram.webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web | ≥ 1.0.41&&< 1.0.83 | 1.0.83com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web:1.0.83 |
Affected Products
digital experience platformliferayliferay portalliferayDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.liferay.commerce:com.liferay.commerce.shop.by.diagram.web to 1.0.83 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-43829 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2025-43829 in your dependencies?
Find it across Maven, including transitive dependencies.