CVE-2024-26272
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 · uneditedCross-site request forgery (CSRF) vulnerability in the content page editor in Liferay Portal 7.3.2 through 7.4.3.107, 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 GA 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 p_l_back_url 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 confidenceCSRF vulnerability in Liferay Portal/DXP content page editor allows attackers to trick authenticated administrators into executing privileged actions via the p_l_back_url parameter. Successful exploitation enables password changes, server shutdown, and arbitrary code execution through the scripting console.
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>= 2023.q3.1, < 2023.q3.6>= 2023.q4.0, < 2023.q4.3= 7.3= 7.4>= 7.3.2, <= 7.3.7>= 7.4.0, < 7.4.3.108CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Liffel Portal or DXP versionCheck the product version in the Control Panel under Configuration > Server Administration > Product Information, or inspect the portal-ext.properties file for the version propertyAffected if The installed version falls within any of these ranges: Liffel DXP 2023.q3.1 through 2023.q3.5, 2023.q4.0 through 2023.q4.2, 7.3.x, or 7.4.x (below 7.4.3.108); or Liffel Portal 7.3.2 through 7.3.7, or 7.4.0 through 7.4.3.107
-
Verify administrative access to content page editorLog in as an administrator and navigate to Site Builder > Pages > Content Page Editor, or attempt to access the /content-page-editor endpointAffected if The content page editor interface is accessible and functional for authenticated administrators
-
Confirm CSRF protection status on administrative endpointsInspect the HTTP responses when submitting forms in the administrative interface. Check if a CSRF token (typically named p_p_auth or similar) is included in POST requests to sensitive endpoints like user management or server actionsAffected if Administrative form submissions lack CSRF token validation and rely solely on session authentication
-
Check for vulnerable p_l_back_url parameter handlingReview server logs or proxy traffic for requests containing the p_l_back_url parameter, particularly those submitted from the content page editor that trigger administrative actions like user password changes or server shutdownAffected if Requests with p_l_back_url from the content page editor are processed without additional CSRF validation
If the installed Liffel Portal or DXP version is within the affected ranges listed and administrative endpoints lack CSRF token enforcement, the environment is vulnerable to CVE-2024-26272.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.4.3.1082023.q3.62023.q4.3
Apply vendor-supplied patches: L Portal 7.4.3.108+ or upgrade to later supported versions, and apply corresponding DXP updates. Implement CSRF tokens for all administrative endpoints as defense-in-depth.
2023.q3.6 / 2023.q4.3 / 7.4.3.108 (depending on product line)
- 1. Identify the current Liferay Portal or DXP version by checking the Liferray Portal/ DXP control panel or server logs
- 2. For Digital Experience Platform users: upgrade to version 2023.q3.6 or later for the 2023.Q3 branch, or upgrade to version 2023.q4.3 or later for the 2023.Q4 branch
- 3. For LPortal 7.4.x users: upgrade to version 7.4.3.108 or later
- 4. For LPortal 7.3.x users: upgrade to the latest 7.3.x version that includes the fix (7.3.8 or later if available)
- 5. After upgrade, verify the content page editor functions correctly and review admin users to confirm no unauthorized changes were made
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-26272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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