dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2025-43795

MEDIUM · 6.1 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 7.3 / 7.4.3.102 or later.
See remediation →
68/100
Remediation priority · Elevated
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
Open redirect vulnerability in the System Settings in Liferay Portal 7.1.0 through 7.4.3.101, and Liferay DXP 2023.Q3.1 through 2023.Q3.4 , 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to redirect users to arbitrary external URLs via the _com_liferay_configuration_admin_web_portlet_SystemSettingsPortlet_redirect parameter. Open redirect vulnerability in the Instance Settings in Liferay Portal 7.1.0 through 7.4.3.101, and Liferay DXP 2023.Q3.1 through 2023.Q3.4 , 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to redirect users to arbitrary external URLs via the _com_liferay_configuration_admin_web_portlet_InstanceSettingsPortlet_redirect parameter. Open redirect vulnerability in the Site Settings in Liferay Portal 7.1.0 through 7.4.3.101, and Liferay DXP 2023.Q3.1 through 2023.Q3.4 , 7.4 GA through update 92, 7.3 GA through update 35, and older unsupported versions allows remote attackers to redirect users to arbitrary external URLs via the _com_liferay_site_admin_web_portlet_SiteSettingsPortlet_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

Open redirect vulnerability in Liferay Portal and DXP affecting three portlets (SystemSettingsPortlet, InstanceSettingsPortlet, and SiteSettingsPortlet) via the 'redirect' parameter. Attackers can craft malicious URLs that redirect authenticated users to external malicious sites, enabling phishing attacks.

MitigationApply vendor-provided patches or upgrade to a supported L versions that include proper validation of the redirect parameter to ensure only internal URLs are allowed.

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.3>= 2023.Q3.0, < 2023.Q3.5= 7.3= 7.4
Liferay PortalApplication
Affected:>= 7.1.0, < 7.4.3.102

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 your Lifer Portal or DXP version
    Locate the version through the Lifer Control Panel (Control Panel > Configuration > System Information > Lifer), or check the portal-ext.properties file, or examine the WAR file version metadata
    Affected if The installed version is: Lifer DXP < 7.3, or >= 2023.Q3.0 and < 2023.Q3.5, or = 7.3, or = 7.4; OR Lifer Portal >= 7.1.0 and < 7.4.3.102
  2. Confirm the three vulnerable portlets are deployed
    Check the deployed portlet WAR files or examine the Lifer portlet registry for SystemSettingsPortlet, InstanceSettingsPortlet, and SiteSettingsPortlet
    Affected if Any of these three portlets are installed and enabled in the Lifer environment
  3. Verify the portlets are accessible to authenticated users
    Log in as an authenticated user and navigate to the Control Panel sections where these portlets appear (System Settings, Instance Settings, or Site Settings), or inspect the portlet permissions configuration
    Affected if Authenticated users can access the SystemSettingsPortlet, InstanceSettingsPortlet, or SiteSettingsPortlet interfaces
  4. Inspect URL handling for the redirect parameter
    Examine HTTP requests and responses when using these portlets, looking for URLs that include a 'redirect' parameter, or review the portlet configuration for redirect handling
    Affected if The portlets generate or process URLs containing a 'redirect' parameter that can be manipulated
  5. Test for open redirect behavior
    With an authenticated session, access a portlet URL with a crafted redirect parameter pointing to an external domain (for example: redirect=http://malicious-site.com), and observe whether Lifer allows the external redirect
    Affected if The application redirects to an external domain when the redirect parameter is set to a URL outside the Lifer domain

Your environment is affected if you are running a Lifer Portal or DXP version within the affected ranges AND the SystemSettingsPortlet, InstanceSettingsPortlet, or SiteSettingsPortlet are accessible to authenticated users who can trigger external redirects via the redirect 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.3 / 7.4.3.102 / 2023.Q3.5 or later
Fixed in 7.37.4.3.1022023.Q3.5
Interim mitigation

Apply vendor-provided patches or upgrade to a supported L versions that include proper validation of the redirect parameter to ensure only internal URLs are allowed.

Recommended fix High confidence

Lifer Portal 7.4.3.102+ / Lifer DXP 2023.Q3.5+ / DXP 7.3 update 35+ / DXP 7.4 update 92+

  1. 1. Identify the currently running Lifer Portal or DXP version by checking the Lifer Portal Control Panel > Configuration > Server Administration.
  2. 2. Determine the product type (Lifer Portal vs. Lifer DXP) and current update version.
  3. 3. For Lifer Portal 7.1.x through 7.4.3.101: Upgrade to Lifer Portal 7.4.3.102 or later.
  4. 4. For Lifer DXP 2023.Q3.x (x < 5): Upgrade to DXP 2023.Q3.5 or later.
  5. 5. For Lifer DXP 7.3.x (update < 35): Upgrade to DXP 7.3 update 35 or later.
  6. 6. For Lifer DXP 7.4.x (update < 92): Upgrade to DXP 7.4 update 92 or later.
  7. 7. After upgrade, verify the _redirect parameters in System Settings, Instance Settings, and Site Settings ports no longer accept external URLs.
  8. 8. Test that legitimate redirect functionality still works for internal paths.
Caveat Minor: Upgrading across major versions may require compatibility testing with custom plugins/themes; ensure test environment validation before production deployment

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,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 $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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