dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43823

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-07
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.q3.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-site scripting (XSS) vulnerability in the Commerce Search Result widget in Liferay Portal 7.4.0 through 7.4.3.111, and Liferay DXP 2023.Q4 before patch 6, 2023.Q3 before patch 9, and 7.4 GA through update 92 allows remote attackers to inject arbitrary web script or HTML via a crafted payload injected into a Commerce Product's Name text field.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored XSS vulnerability exists in the Lifer Commerce Search Result widget where the Commerce Product Name field is not properly sanitized before rendering. Attackers can inject malicious JavaScript/HTML into the Product Name, which executes when users view the search results.

MitigationApply the vendor patches for the affected Lifer Portal/DXP versions (2023.Q4 patch 6, 2023.Q3 patch 9, or 7.4 update 93+). As a temporary workaround, restrict Commerce Product creation permissions to trusted users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Digital Experience PlatformApplication
Affected:>= 2023.q3.1, < 2023.q3.9>= 2023.q4.0, < 2023.q4.6= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.112

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lifer Portal/DXP version
    Access the Lifer Control Panel > Configuration > Server Administration > Product Information, or check the portal-ext.properties file for the version property
    Affected if The version falls within >= 2023.q3.1 and < 2023.q3.9, OR >= 2023.q4.0 and < 2023.q4.6, OR equals 7.4, OR >= 7.4.0 and < 7.4.3.112
  2. Verify Commerce module is enabled
    Navigate to Control Panel > Apps > Lifer Marketplace, search for Commerce, and confirm it is installed and active
    Affected if Commerce module is installed and running on the system
  3. Confirm Search Result widget usage
    Check Site Pages for any instance of the Commerce Search Result widget, or review the widget configuration in the Lifer page editor
    Affected if The Commerce Search Result widget is added to any page in the environment
  4. Review Commerce Product creation permissions
    Go to Control Panel > Users > Roles, locate the Commerce Product creator role, and check which users or organizations are assigned permission to create Commerce Products
    Affected if Multiple untrusted users or external roles have permissions to create or edit Commerce Products, allowing potential injection of malicious Product Names

You are affected if running an affected Lifer version with the Commerce module and Search Result widget enabled, and untrusted users can create Commerce Products whose names could be rendered without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.4.3.112 / 2023.q3.9 / 2023.q4.6 or later
Fixed in 7.4.3.1122023.q3.92023.q4.6
Interim mitigation

Apply the vendor patches for the affected Lifer Portal/DXP versions (2023.Q4 patch 6, 2023.Q3 patch 9, or 7.4 update 93+). As a temporary workaround, restrict Commerce Product creation permissions to trusted users only.

Recommended fix High confidence

Liferay Portal 7.4.3.112+; Lifford DXP 2023.q3.9+; Lifford DXP 2023.q4.6+

  1. 1. Identify the exact Lifford product and version currently deployed (Portal or DXP, and specific version number)
  2. 2. For Lifford Portal 7.4.x users: Upgrade to version 7.4.3.112 or later
  3. 3. For Lifford DXP 2023.Q3 users: Apply patch 9 or later (upgrade to 2023.q3.9 or later)
  4. 4. For Lifford DXP 2023.Q4 users: Apply patch 6 or later (upgrade to 2023.q4.6 or later)
  5. 5. After upgrade, verify the Commerce Search Result widget functions correctly with the fixed version
  6. 6. Test that the Commerce Product Name field properly sanitizes input to confirm the XSS fix is applied
Caveat Review Lifford release notes for any breaking changes between current version and target fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43823 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data