dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-26273

HIGH · 8.8 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 7.4.3.104 / 2023.q3.6 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Cross-site request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.4.0 through 7.4.3.103, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, 2023.Q3.1 through 2023.Q3.5, 7.4 GA through update 92 and 7.3 update 29 through update 35 allows remote attackers to (1) change user passwords, (2) shut down the server, (3) execute arbitrary code in the scripting console, (4) and perform other administrative actions via the _com_liferay_commerce_catalog_web_internal_portlet_CommerceCatalogsPortlet_redirect parameter.

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

CSRF vulnerability in Lifer Portal and DXP content page editor allows authenticated administrators to be tricked into performing unauthorized administrative actions (password changes, server shutdown, arbitrary code execution) via the CommerceCatalogsPortlet redirect parameter.

MitigationApply vendor patches: Lifer Portal 7.4.x users should upgrade to 7.4.3.104+, DXP users should apply the appropriate hotfix for their version (2023.Q4.3+, 2023.Q3.6+, or respective update packages).

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.6>= 2023.q4.0, < 2023.q4.3= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.4.0, < 7.4.3.104

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 product type
    Determine if your installation is Lifer Portal or Lifer DXP. Check application startup logs, the welcome page footer, or the control panel for the product name.
    Affected if The product is Lifer Portal or Lifer Digital Experience Platform.
  2. Check installed version against affected ranges
    Locate the version file or check the control panel for the exact version number. Compare against: DXP >= 2023.q3.1 AND < 2023.q3.6; DXP >= 2023.q4.0 AND < 2023.q4.3; DXP = 7.3; DXP = 7.4; Portal >= 7.4.0 AND < 7.4.3.104
    Affected if Your version falls within any of these ranges.
  3. Verify CommerceCatalogsPortlet is accessible
    Check if the Commerce Catalog portlet is deployed and accessible in your Lifer instance. Look for the portlet named 'CommerceCatalogsPortlet' or 'com_lifer_commerce_catalog_web_internal_portlet_CommerceCatalogsPortlet' in the portlet registry or control panel.
    Affected if The CommerceCatalogsPortlet is deployed and accessible to authenticated users.
  4. Inspect for vulnerable redirect parameter
    Review application logs or proxy logs for requests containing the parameter '_com_lifer_commerce_catalog_web_internal_portlet_CommerceCatalogsPortlet_redirect' with unexpected values, especially those containing URL-encoded JavaScript or administrative endpoints.
    Affected if Requests with this parameter are being processed by your instance.

You are affected if you are running a Lifer Portal or DXP version within the affected ranges AND the CommerceCatalogsPortlet is accessible to authenticated administrators, allowing the CSRF attack surface to exist.

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.104 / 2023.q3.6 / 2023.q4.3 or later
Fixed in 7.4.3.1042023.q3.62023.q4.3
Interim mitigation

Apply vendor patches: Lifer Portal 7.4.x users should upgrade to 7.4.3.104+, DXP users should apply the appropriate hotfix for their version (2023.Q4.3+, 2023.Q3.6+, or respective update packages).

Recommended fix High confidence

Lifer Portal 7.4.3.104+ / DXP 2023.q3.6+ / DXP 2023.q4.3+ / DXP 7.4 update 93+ / DXP 7.3 update 36+

  1. 1. Identify the current L安装 (Lifer Portal or DXP) version using the Server Administration console or help/about page
  2. 2. For Lifer Portal 7.4.x: Upgrade to version 7.4.3.104 or later
  3. 3. For DXP 2023.Q3.x: Upgrade to version 2023.q3.6 or later
  4. 4. For DXP 2023.Q4.x: Upgrade to version 2023.q4.3 or later
  5. 5. For DXP 7.3: Upgrade to update 36 or later
  6. 6. For DXP 7.4 GA: Upgrade to update 93 or later
  7. 7. After upgrade, verify the fix by confirming the _com_lifer_commerce_catalog_web_internal_portlet_CommerceCatalogsPortlet_redirect parameter is no longer vulnerable to CSRF attacks
Caveat Standard upgrade considerations apply - review Lifer's upgrade documentation for database migration, compatibility with custom plugins, and backup procedures before proceeding

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
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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