# CVE-2023-5190: Liferay Portal and Liferay DXP Vulnerable to Open Redirect in Countries Management's Edit Region Page > Remote attackers can redirect users to arbitrary external URLs via a specific parameter in the Countries Management edit region page. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 20 Feb 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-f3rf-cr7f-cwc4 ## What is CVE-2023-5190? CVE-2023-5190 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2023-5190? 6 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay.portal:release.portal.bom. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3 | 2023.Q3.6 | | `com.liferay.portal:release.dxp.bom` | Maven | From 2023.Q3 | 2023.Q3.6 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u45 to 7.4.13.u92 | None | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u45 to 7.4.13.u92 | None | | `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.45-ga45 | 7.4.3.102-ga102 | | `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.45-ga45 | 7.4.3.102-ga102 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2023-5190? Upgrade com.liferay.portal:release.dxp.bom to 2023.Q3.6 or later. ## Is CVE-2023-5190 being exploited? There is no known exploitation of CVE-2023-5190 in the wild and no public exploit code. ## Other vulnerabilities in Liferay Digital Experience Platform - [CVE-2024-8980](https://insights.sbomify.com/CVE-2024-8980/): Liferay Portal and Liferay DXP Vulnerable to CSRF in the Script Console (critical 9.6) - [CVE-2023-42496](https://insights.sbomify.com/CVE-2023-42496/): Liferay Portal and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6) - [CVE-2023-42498](https://insights.sbomify.com/CVE-2023-42498/): Liferay Portal Language Override edit screen and Liferay DXP vulnerable to reflected Cross-site Scripting (critical 9.6) - [CVE-2024-25147](https://insights.sbomify.com/CVE-2024-25147/): Liferay Portal and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6) - [CVE-2024-26269](https://insights.sbomify.com/CVE-2024-26269/): Liferay Portal Frontend JS module's portlet.js and Liferay DXP vulnerable to Cross-site Scripting (critical 9.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-5190 and fix it if it is affected. What it is: CVE-2023-5190 is a medium-severity vulnerability in Liferay Digital Experience Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-5190 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3; fixed in 2023.Q3.6 - com.liferay.portal:release.dxp.bom (Maven): affected from 2023.Q3; fixed in 2023.Q3.6 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.13.u45 up to 7.4.13.u92; no fix listed - com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.13.u45 up to 7.4.13.u92; no fix listed - com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.45-ga45; fixed in 7.4.3.102-ga102 - com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.45-ga45; fixed in 7.4.3.102-ga102 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-5190/ (Markdown: https://insights.sbomify.com/CVE-2023-5190/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5190 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5190 - OSV: https://osv.dev/vulnerability/CVE-2023-5190 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-5190/ Summaries are generated and may contain mistakes; the official description above is the record.