dbcve.org
Digital Experience PlatformApplication · Liferay

CVE-2023-5190

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-20
Fix available
A fix is available. Upgrade to 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 Countries Management’s edit region page in Liferay Portal 7.4.3.45 through 7.4.3.101, and Liferay DXP 2023.Q3 before patch 6, and 7.4 update 45 through 92 allows remote attackers to redirect users to arbitrary external URLs via the _com_liferay_address_web_internal_portlet_CountriesManagementAdminPortlet_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/DXP's Countries Management admin portlet allows attackers to manipulate the _com_lifera_address_web_internal_portlet_CountriesManagementAdminPortlet_redirect parameter to redirect authenticated users to arbitrary external URLs, potentially enabling phishing attacks.

MitigationApply vendor patches (7.4.3.101+, patch 6 for 2023.Q3, or update 92+) to fix the improper redirect validation. Until patched, restrict admin portlet access to trusted users only and monitor for suspicious redirect patterns.

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.4= 2023.q3.0= 2023.q3.1= 2023.q3.2= 2023.q3.3= 2023.q3.4= 2023.q3.5
Liferay PortalApplication
Affected:>= 7.4.3.45, < 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 installed Lifter Portal or DXP version
    Check the Lifer portal or DXP version through the Control Panel > Configuration > Server Administration > Product Information, or inspect the portal-ext.properties file for version properties.
    Affected if The installed version matches 7.4.x, 2023.q3.x (any of .0 through .5), or falls between 7.4.3.45 and 7.4.3.101 inclusive.
  2. Verify the Countries Management admin portlet is deployed
    Check if the CountriesManagementAdminPortlet (portlet ID: com_lifera_address_web_internal_portlet_CountriesManagementAdminPortlet) exists in the deployed web applications or look for the address-web module in the osgi/modules folder.
    Affected if The portlet is present in the deployment.
  3. Confirm user authentication is active for the admin interface
    Review the portal's authentication settings and check if the admin portlet is accessible to authenticated users, particularly those with minimal Country management permissions.
    Affected if Authenticated users can access the Countries Management portlet.
  4. Inspect for suspicious redirect parameter patterns in logs
    Search access and portal logs for requests containing '_com_lifera_address_web_internal_portlet_CountriesManagementAdminPortlet_redirect=' with external domains (URLs not matching the portal's own domain).

A Lifer installation is affected if it runs a version between 7.4.3.45 and 7.4.3.101, or any 7.4, 2023.q3.0 through 2023.q3.5 release, and the Countries Management admin portlet is accessible to authenticated users who could be redirected to external sites.

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.102 or later
Fixed in 7.4.3.102
Interim mitigation

Apply vendor patches (7.4.3.101+, patch 6 for 2023.Q3, or update 92+) to fix the improper redirect validation. Until patched, restrict admin portlet access to trusted users only and monitor for suspicious redirect patterns.

Recommended fix High confidence

L Portal 7.4.3.102+ or DXP 2023.Q3 Patch 6+ or DXP 7.4 update 93+

  1. 1. Identify the current L Portal or DXP version in your deployment
  2. 2. For L Portal 7.4.x deployments: upgrade to version 7.4.3.102 or later
  3. 3. For DXP 2023.Q3 deployments: apply Lifer DXP 2023.Q3 Patch 6 or later
  4. 4. For DXP 7.4 update 45-92 deployments: upgrade to the first DXP 7.4 update released after update 92 that contains the security fix
  5. 5. After upgrading, verify the Countries Management admin portlet is functioning correctly and the redirect parameter is properly validated
Caveat Review Lifer release notes for your specific upgrade path as minor version upgrades may include feature changes

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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