CVE-2023-42627 — com.liferay.commerce.addr…
MEDIUMCVE-2023-42627 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in com.liferay.commerce:com.liferay.commerce.address.content.web. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.liferay.commerce:com.liferay.commerce.address.content.web — see the affected versions and patch details below.
Liferay Portal and Liferay DXP Vulnerable to XSS in the Commerce Module
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- 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-2023-42627.
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.address.content.web☕com.liferay.portal:release.dxp.bom☕com.liferay.portal:release.dxp.bomReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.liferay.commerce:com.liferay.commerce.address.content.web | all versions | 4.0.35com.liferay.commerce:com.liferay.commerce.address.content.web:4.0.35 |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.3.0 | No fix |
| ☕Maven | com.liferay.portal:release.dxp.bom | ≥ 7.4.0 | No fix |
Affected Products
digital experience platformliferayliferay portalliferayResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & 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.address.content.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.address.content.web to 4.0.35 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-42627 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-2023-42627 in your dependencies?
Find it across Maven, including transitive dependencies.