# CVE-2023-3426: Liferay Portal and Liferay DXP Organization Selector Does Not Check User Permissions

> Authenticated users can bypass permission checks to view all organizations in Liferay Portal, exposing sensitive organizational data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Aug 2023
- **Updated:** 11 Oct 2024
- **Also known as:** BIT-liferay-2023-3426, GHSA-xph3-vjcq-g488

## What is CVE-2023-3426?

CVE-2023-3426 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 2 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The organization selector in Liferay Portal 7.4.3.81 through 7.4.3.85, and Liferay DXP 7.4 update 81 through 85 does not check user permission, which allows remote authenticated users to obtain a list of all organizations.

Weakness: CWE-862 (Missing Authorization), CWE-425 (Direct Request)

## Which versions are affected by CVE-2023-3426?

5 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom, liferay and com.liferay:com.liferay.organizations.item.selector.web. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.143.u81 to 7.4.143.u85 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.143.u81 to 7.4.143.u85 | None |
| `liferay` | Bitnami | From 7.4-update81.0 to 7.4-update81.0 | None |
| `com.liferay:com.liferay.organizations.item.selector.web` | Maven | All versions | 4.0.14 |
| `com.liferay:com.liferay.organizations.item.selector.web` | Maven | All versions | 4.0.14 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2023-3426?

Apply the vendor's patch.

## Is CVE-2023-3426 being exploited?

There is no known exploitation of CVE-2023-3426 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-3426 and fix it if it is affected.

What it is: CVE-2023-3426 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 2 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-3426 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.143.u81 up to 7.4.143.u85; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.143.u81 up to 7.4.143.u85; no fix listed
- liferay (Bitnami): affected from 7.4-update81.0 up to 7.4-update81.0; no fix listed
- com.liferay:com.liferay.organizations.item.selector.web (Maven): affected all versions; fixed in 4.0.14
- com.liferay:com.liferay.organizations.item.selector.web (Maven): affected all versions; fixed in 4.0.14

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-3426/ (Markdown: https://insights.sbomify.com/CVE-2023-3426/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-3426
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-3426
- OSV: https://osv.dev/vulnerability/CVE-2023-3426

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-3426/
Summaries are generated and may contain mistakes; the official description above is the record.