dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2024-26271

HIGH · 8.8 CVSS v3.1 Published 2024-10-22
Fix available
A fix is available. Upgrade to 7.4.3.112 / 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 My Account widget in Liferay Portal 7.4.3.75 through 7.4.3.111, and Liferay DXP 2023.Q4.0 through 2023.Q4.2, 2023.Q3.1 through 2023.Q3.5, 7.4 update 75 through update 92 and 7.3 update 32 through update 36 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_my_account_web_portlet_MyAccountPortlet_backURL 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

This is a CSRF vulnerability in Liferays My Account widget where the _com_lifera_my_account_web_portlet_MyAccountPortlet_backURL parameter lacks proper anti-CSRF tokens. Attackers can trick authenticated users into unknowingly triggering administrative actions including password changes, server shutdown, and arbitrary code execution via the scripting console.

MitigationApply the vendor patches or upgrade to Liferay Portal 7.4.3.112+, Liferay DXP 2023.Q4.3+, or later supported versions that include CSRF protection for the affected My Account widget endpoints.

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.3.75, < 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
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 Liferay Portal version
    Access the Liferay Control Panel or check the portal.properties file for the version number (e.g., look for portal.version or build.number)
    Affected if The version is 7.3.x, 7.4.x between 7.4.3.75 and 7.4.3.111, or falls within 2023.q3.1 to 2023.q3.5, or 2023.q4.0 to 2023.q4.2
  2. Identify Liferay DXP version
    Check the Liferay Digital Experience Platform version through the Control Panel or portal-ext.properties file
    Affected if The version is 7.3.x, 7.4.x, 2023.q3.1 through 2023.q3.5, or 2023.q4.0 through 2023.q4.2
  3. Confirm My Account portlet is deployed
    Log in as an administrator and navigate to the My Account widget or portlet in the portal. Check if the portlet is accessible at /c/portlet/my_account or similar My Account functionality
    Affected if The My Account portlet is present and accessible to authenticated users
  4. Inspect the My Account form for CSRF token
    View the page source or intercept the HTTP response when loading the My Account portlet. Look for a hidden input field containing a CSRF token (commonly named _com_liferay_my_account_web_portlet_MyAccountPortlet_p_auth or similar)
    Affected if The form lacks a visible CSRF token parameter for the _com_liferay_my_account_web_portlet_MyAccountPortlet_backURL parameter or no p_auth token is present in the form submission
  5. Test for CSRF vulnerability
    Create a malicious page with a form that auto-submits to the My Account portlet endpoint using the backURL parameter without a valid CSRF token. Monitor if the action executes successfully
    Affected if The backend accepts requests to the My Account portlet without validating anti-CSRF tokens for the backURL parameter

You are affected if your Liferay Portal or DXP version falls within the specified ranges and the My Account portlet accepts requests without validating CSRF tokens on the backURL parameter.

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

Apply the vendor patches or upgrade to Liferay Portal 7.4.3.112+, Liferay DXP 2023.Q4.3+, or later supported versions that include CSRF protection for the affected My Account widget endpoints.

Recommended fix High confidence

Lifera DXP 2023.Q3.6, 2023.Q4.3, or Lifera Portal 7.4.3.112 (or latest supported version on your branch)

  1. 1. Identify your current Lifera Portal or DXP version by checking the Control Panel > Configuration > Server Administration > Version
  2. 2. For DXP 2023.Q3.x users: Upgrade to version 2023.Q3.6 or later
  3. 3. For DXP 2023.Q4.x users: Upgrade to version 2023.Q4.3 or later
  4. 4. For Lifera Portal 7.4.x users: Upgrade to version 7.4.3.112 or later
  5. 5. For Lifera DXP 7.3.x users: Upgrade to the latest supported 7.3.x version (7.3 update 37 or later if available), or migrate to a supported version branch
  6. 6. After upgrade, verify the My Account widget functions correctly and test that CSRF protection is working
Caveat Review Lifera's upgrade documentation for your specific version jump as there may be breaking changes between major update releases; test thoroughly in a non-production environment first

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-2024-26271 — 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-26271 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