dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43779

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-24
Fix available
A fix is available. Upgrade to 7.4.3.113 / 2024.Q1.19 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
A reflected cross-site scripting (XSS) vulnerability in the Liferay Portal 7.4.0 through 7.4.3.112, and Liferay DXP 2024.Q1.1 through 2024.Q1.18 and 7.4 GA through update 92 allows a remote authenticated attacker to inject JavaScript code via _com_liferay_commerce_product_definitions_web_internal_portlet_CPDefinitionsPortlet_productTypeName parameter. This malicious payload is then reflected and executed within the user's browser.

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 reflected cross-site scripting (XSS) vulnerability exists in LPortal 7.4.0-7.4.3.112 and L DXP 2024.Q1.1-2024.Q1.18/7.4 GA-92. The _com_liferay_commerce_product_definitions_web_internal_portlet_CPDefinitionsPortlet_productTypeName parameter accepts unsanitized user input that gets reflected back in the response, allowing JavaScript execution in victim browsers when they access a crafted link.

MitigationImplement proper input validation and output encoding on the productTypeName parameter in CPDefinitionsPortlet to neutralize malicious script payloads before reflection.

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:>= 2024.Q1.1, < 2024.Q1.19= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.113

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Liferay version
    Check the portal's version by reviewing the release.properties file in the Liferay home directory, or access the Control Panel > Configuration > Server Administration > Version. Look for the exact version number such as 7.4.3.112, 2024.Q1.18, or similar.
    Affected if The installed version is 7.4.0 through 7.4.3.112, or 2024.Q1.1 through 2024.Q1.18, or matches 7.4 GA-92.
  2. Confirm CPDefinitionsPortlet is accessible
    Navigate to the Commerce Product Definitions portlet in the Liferay Control Panel. Access the Products section under Commerce. The vulnerable endpoint is typically at /c/portal/layout?p_l_id=...&_com_liferay_commerce_product_definitions_web_internal_portlet_CPDefinitionsPortlet_productTypeName=...
    Affected if The portlet is accessible and accepts the productTypeName parameter.
  3. Test for reflected parameter behavior
    Send a request to the CPDefinitionsPortlet with a test value in the productTypeName parameter, such as productTypeName=test123, and examine if the response reflects this value in the HTML without proper encoding.
    Affected if The parameter value is reflected unsanitized in the response HTML.
  4. Check for absence of input validation
    Inspect the HTTP response headers and body when submitting special characters like <script>alert(1)</script> in the productTypeName parameter. Verify if these characters are rendered as-is or are properly encoded.
    Affected if Special characters or script tags appear unencoded in the response.

You are affected if your LPortal version is between 7.4.0 and 7.4.3.112 inclusive, or your L DXP version is between 2024.Q1.1 and 2024.Q1.18 inclusive, and the CPDefinitionsPortlet with the productTypeName parameter is accessible and reflects unsanitized input.

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.113 / 2024.Q1.19 or later
Fixed in 7.4.3.1132024.Q1.19
Interim mitigation

Implement proper input validation and output encoding on the productTypeName parameter in CPDefinitionsPortlet to neutralize malicious script payloads before reflection.

Recommended fix High confidence

Lifera Portal 7.4.3.113+ or Liferay DXP 2024.Q1.19+ / 7.4 Update 93+

  1. 1. Backup your current L installation before proceeding with any upgrade.
  2. 2. For Lifera Portal 7.4.x users: Upgrade to version 7.4.3.113 or later.
  3. 3. For Liferay DXP 2024.Q1.x users: Upgrade to version 2024.Q1.19 or later.
  4. 4. For Liferay DXP 7.4 users: Upgrade to update 93 or later.
  5. 5. After upgrading, verify the _com_lifteray_commerce_product_definitions_web_internal_portlet_CPDefinitionsPortlet_productTypeName parameter is properly encoded/validated.
  6. 6. Test that the commerce product definitions portlet functions correctly after the upgrade.
  7. 7. Verify the XSS vulnerability is no longer exploitable by attempting to inject JavaScript via the affected parameter.

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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