dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43821

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-08
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 Product Comparison Table widget in Liferay Portal 7.4.0 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 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

Stored XSS vulnerability in Lifer Portal's Commerce Product Comparison Table widget allows attackers to inject malicious scripts into the Commerce Product Name field, which executes when users view the product comparison table.

MitigationUpdate to Lifer DXP 7.4 GA update 93 or later (or corresponding patched versions for DXP 2023.Q3/Q4 releases) to obtain the vendor patch; alternatively, implement input sanitization on the Product Name field before rendering.

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 or DXP installation version
    Access the Control Panel > Configuration > Server Administration > Product Information, or locate the liferay-version.properties file in the bundle. Alternatively, check the login page footer which often displays the version.
    Affected if The version is 7.4.0 through 7.4.3.111, or falls within 2023.q3.1 through 2023.q3.8, or 2023.q4.0 through 2023.q4.5.
  2. Confirm Commerce module is enabled
    Navigate to Control Panel > Apps > App Manager, or check for the presence of the 'Commerce' menu option in the Control Panel sidebar.
    Affected if Commerce is installed and enabled on the Lifer instance.
  3. Locate Commerce Product Comparison Table widget instances
    Go to Site Administration > Pages > Pages, then use the Page Search or inspect each page in edit mode to find instances of the 'Product Comparison Table' widget within a Commerce widget page or widget frame.
    Affected if The Product Comparison Table widget is present on any published page.
  4. Inspect Commerce Product catalog entries
    Access the Commerce Admin menu (Commerce > Products) and review the product names stored in the catalog. If you have admin access, you can query the Commerce database table (typically CommerceProduct or CommerceProductEntry) for the name field.
    Affected if Any product names exist in the catalog, particularly if they were entered by users without input sanitization.

You are affected if your Lifer Portal/DXP version is within the vulnerable ranges AND the Commerce module with the Product Comparison Table widget is enabled and populated with products.

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

Update to Lifer DXP 7.4 GA update 93 or later (or corresponding patched versions for DXP 2023.Q3/Q4 releases) to obtain the vendor patch; alternatively, implement input sanitization on the Product Name field before rendering.

Recommended fix High confidence

Lifter Portal: 7.4.3.112+ | DXP 2023.Q3: 2023.Q3.9+ | DXP 2023.Q4: 2023.Q4.6+ | DXP 7.4: updates beyond 92

  1. 1. Identify the exact Liferay product and version currently running (Portal or Digital Experience Platform, and the specific version number)
  2. 2. For Liferay Portal 7.4.0-7.4.3.111: upgrade to version 7.4.3.112 or later
  3. 3. For Liferay DXP 2023.Q3.1-2023.Q3.8: upgrade to version 2023.Q3.9
  4. 4. For Liferay DXP 2023.Q4.0-2023.Q4.5: upgrade to version 2023.Q4.6
  5. 5. For Liferay DXP 7.4 GA: upgrade to a version receiving updates beyond update 92
  6. 6. After upgrade, verify the Commerce Product Comparison Table widget functions correctly and test that XSS payloads in product names are no longer executable
Caveat Standard upgrade considerations apply - review Liferay's upgrade documentation for your version path, especially regarding database schema changes and compatibility with existing themes/plugins

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

Fix this in Digital Experience Platform Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-43821 — 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-43821 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