dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43748

MEDIUM · 6.8 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to 7.4.3.120 / 2024.Q1.7 or later.
See remediation →
72/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
Insufficient CSRF protection for omni-administrator users in Liferay Portal 7.0.0 through 7.4.3.119, and Liferay DXP 2024.Q1.1 through 2024.Q1.6, 2023.Q4.0 through 2023.Q4.9, 2023.Q3.1 through 2023.Q3.9, 7.4 GA through update 92, 7.3 GA through update 36, and older unsupported versions allows attackers to execute Cross-Site Request Forgery

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

Lifera Portal and DXP have insufficient CSRF protection for omni-administrator users, allowing attackers to craft malicious requests that an authenticated administrator unknowingly executes. The vulnerability stems from missing or inadequate anti-CSRF token validation on administrative actions.

MitigationApply the vendor-provided security update/patch for this vulnerability. As an immediate defensive measure, configure the application to validate Origin and Referer headers on sensitive admin operations.

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:>= 7.0, <= 7.4>= 2023.Q3.1, <= 2023.Q3.9>= 2023.Q4.0, <= 2023.Q4.9>= 2024.Q1.1, < 2024.Q1.7
Liferay PortalApplication
Affected:>= 7.0.0, < 7.4.3.120= 6.2

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
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Check Liferay Portal/DXP version
    Log in as an administrator and navigate to Control Panel > Configuration > Server Administration > General, or check the portal-version property in portal.properties or portal-ext.properties
    Affected if The installed version falls within these ranges: DXP 7.0-7.4, 2023.Q3.1-2023.Q3.9, 2023.Q4.0-2023.Q4.9, 2024.Q1.1-2024.Q1.6; or Portal 7.0.0-7.4.3.119, or Portal 6.2
  2. Verify CSRF token configuration in portal.properties
    Open portal-ext.properties or portal.properties and search for properties related to CSRF protection such as 'csrf.token.enabled' or 'auth.token.enabled'
    Affected if The CSRF token validation is disabled, missing, or set to false for administrative actions
  3. Check for anti-CSRF token presence in admin forms
    Log in as an administrator, open browser developer tools, inspect the Network tab, and submit an admin action (e.g., adding a user or modifying settings). Examine the request headers and form parameters for a CSRF token parameter
    Affected if No anti-CSRF token parameter (such as 'p_auth', 'csrfToken', or similar) is present in admin action requests
  4. Verify Origin and Referer header validation
    Check the web.xml or portal's security configuration for CSRF filter settings that validate Origin and Referer headers on sensitive admin endpoints
    Affected if Origin and Referer header validation is not configured or is disabled for admin operations
  5. Confirm omni-administrator access is enabled
    Navigate to Control Panel > Users and Roles > Users and verify that omni-administrator accounts exist or that the portal allows multiple admin sessions
    Affected if Omni-administrator functionality is in use, as the vulnerability specifically affects omni-administrator users

You are affected if your Liferay Portal or DXP version is within the affected ranges AND admin actions lack proper anti-CSRF token validation or header checks.

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.120 / 2024.Q1.7 or later
Fixed in 7.4.3.1202024.Q1.7
Interim mitigation

Apply the vendor-provided security update/patch for this vulnerability. As an immediate defensive measure, configure the application to validate Origin and Referer headers on sensitive admin operations.

Recommended fix High confidence

LiferL Portal 7.4.3.120+ or DXP 2024.Q1.7+ (depending on product)

  1. 1. Identify the currently installed Liferay Portal or DXP version by checking the portal-ext.properties or the control panel About section
  2. 2. For LiferL Portal 7.0-7.4.3.119: Upgrade to LiferL Portal 7.4.3.120 or later
  3. 3. For DXP 2024.Q1.1-2024.Q1.6: Upgrade to DXP 2024.Q1.7 or later
  4. 4. For DXP 2023.Q4.0-2023.Q4.9: Upgrade to DXP 2024.Q1.7 or later (DXP 2023.Q4.x is no longer supported per LiferL's support matrix)
  5. 5. For DXP 2023.Q3.1-2023.Q3.9: Upgrade to DXP 2024.Q1.7 or later
  6. 6. For DXP 7.4 GA (older than update 92): Upgrade to DXP 7.4 update 92 or later, or migrate to 7.4.3.120
  7. 7. For DXP 7.3 GA (older than update 36): Upgrade to DXP 7.3 update 36 or later, or migrate to a supported version
  8. 8. After upgrade, verify the CSRF protection is functioning by testing admin actions
Caveat Review LiferL's upgrade guide for your version jump; major version upgrades may require migration steps and compatibility testing of custom plugins/themes

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
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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