dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43805

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-16
Fix available
A fix is available. Upgrade to 7.4.3.112 / 2023.Q3.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Liferay Portal 7.3.0 through 7.4.3.111, and Liferay DXP 2023.Q4.0, 2023.Q3.1 through 2023.Q3.4, 7.4 GA through update 92, and 7.3 GA through update 35 does not perform an authorization check when users attempt to view a display page template, which allows remote attackers to view display page templates via crafted URLs.

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 versions 7.3.0 through 7.4.3.111 and multiple DXP releases (2023.Q4.0, 2023.Q3.1-2023.Q3.4, 7.4 GA through update 92, 7.3 GA through update 35) lack proper authorization checks when users attempt to view display page templates. This broken access control vulnerability allows remote attackers to access display page templates via crafted URLs without authentication, resulting in unauthorized information disclosure.

MitigationApply Lifera's vendor patches for the affected versions to enforce proper authorization checks on display page template access, and audit existing template permissions to ensure they align with least-privilege principles.

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.0, < 2023.Q3.5= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.3.0, < 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 Portal or DXP version
    Locate the version file in the Liferay installation directory, typically found in portal-impl.jar or via the Control Panel > Configuration > Server Administration > Version. Alternatively, check the portal-ext.properties file for version properties.
    Affected if The installed version is 7.3.0 through 7.4.3.111, or falls within 2023.Q3.0 to 2023.Q3.4, 2023.Q4.0, or is DXP 7.3 GA through update 35, or DXP 7.4 GA through update 92.
  2. Determine if display page templates are configured
    Navigate to Site Builder > Display Page Templates in the Liferay Control Panel, or query the displaypagetemplate table in the Liferay database to list existing templates.
    Affected if Display page templates exist in the environment, making the authorization flaw potentially exploitable.
  3. Verify display page template access permissions
    Review the permission settings for each display page template in the Control Panel under Site Builder > Display Page Templates > Permissions. Check if Guest or Unauthenticated roles have View permission.
    Affected if Guest users or unauthenticated roles have been granted View permission on any display page template.
  4. Test unauthorized template access via URL
    Attempt to access a display page template directly using a crafted URL pattern such as /display_page_template/ or /web/[site-name]/[template-friendly-url] without providing authentication credentials.
    Affected if The template content is returned without requiring authentication, indicating the broken access control is present.
  5. Check for vendor patches applied
    Review the Liferay patch history in the patching tool output or check for the presence of patch files in the /patches/ directory. Look for patch IDs related to CVE-2025-43805.
    Affected if No vendor security patches for CVE-2025-43805 have been applied and the version falls within the affected range.

The environment is affected if the installed Liferay Portal or DXP version falls within the vulnerable range (7.3.0-7.4.3.111 or specific DXP quarterly releases) AND display page templates are accessible without authentication, as evidenced by direct URL access or permissive guest permissions.

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.5 or later
Fixed in 7.4.3.1122023.Q3.5
Interim mitigation

Apply Lifera's vendor patches for the affected versions to enforce proper authorization checks on display page template access, and audit existing template permissions to ensure they align with least-privilege principles.

Recommended fix High confidence

Liferay Portal: 7.4.3.112 or later; DXP 2023.Q3.x: 2023.Q3.5 or later; DXP 2023.Q4.0: upgrade to 2023.Q3.5 or later release

  1. 1. Identify the currently running Lifter Portal or DXP version using the Liferay Server Control Panel or the Gogo shell command 'system:properties' to confirm the exact version.
  2. 2. For Liferay Portal 7.3.x installations: Upgrade to version 7.4.3.112 or later.
  3. 3. For Liferay Portal 7.4.x installations: Upgrade to version 7.4.3.112 or later.
  4. 4. For Liferay DXP 2023.Q3.x installations: Upgrade to version 2023.Q3.5 or later.
  5. 5. For Liferay DXP 2023.Q4.0: Upgrade to version 2023.Q3.5 or a later stable release that includes the fix.
  6. 6. After upgrading, verify that authorization checks are enforced for display page templates by testing with a non-privileged user account.
  7. 7. Review and test custom display page templates to ensure they respect the new authorization controls.
Caveat Minor: Ensure custom display page template permissions are properly configured after upgrade; review any custom URL routing logic that may reference display page templates

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-2025-43805 — 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-43805 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