# CVE-2021-33327: Liferay Portal and Liferay DXP does not properly check user permission > Authenticated users can bypass role visibility restrictions to view Guest and User roles in Liferay Portal. - **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:** 3 Aug 2021 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-22wc-7wmm-v4cc ## What is CVE-2021-33327? CVE-2021-33327 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 3 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description The Portlet Configuration module in Liferay Portal 7.2.0 through 7.3.3, and Liferay DXP 7.0 fix pack pack 93 and 94, 7.1 fix pack 18, and 7.2 before fix pack 8, does not properly check user permission, which allows remote authenticated users to view the Guest and User role even if "Role Visibility" is enabled. Weakness: CWE-276 (Incorrect Default Permissions) ## Which versions are affected by CVE-2021-33327? 8 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay:com.liferay.portlet.configuration.web. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.10.fp93 | 7.0.10.fp95 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.10.fp93 | 7.0.10.fp95 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.10.fp18 | 7.1.10.fp19 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.10.fp18 | 7.1.10.fp19 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp8 | | `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 | 7.2.10.fp8 | | `com.liferay:com.liferay.portlet.configuration.web` | Maven | All versions | 4.0.13 | | `com.liferay:com.liferay.portlet.configuration.web` | Maven | All versions | 4.0.13 | Products: Liferay Digital Experience Platform, Liferay Liferay Portal. ## How do I fix CVE-2021-33327? Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.0.10.fp95, 7.1.10.fp19 or 7.2.10.fp8. ## Is CVE-2021-33327 being exploited? There is no known exploitation of CVE-2021-33327 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-2021-33327 and fix it if it is affected. What it is: CVE-2021-33327 is a medium-severity missing authorization vulnerability in Liferay Digital Experience Platform, published on 3 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-33327 in the wild and no public exploit code. Affected packages and fixed versions: - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.10.fp93; fixed in 7.0.10.fp95 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.10.fp93; fixed in 7.0.10.fp95 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.10.fp18; fixed in 7.1.10.fp19 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.10.fp18; fixed in 7.1.10.fp19 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp8 - com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0; fixed in 7.2.10.fp8 - com.liferay:com.liferay.portlet.configuration.web (Maven): affected all versions; fixed in 4.0.13 - com.liferay:com.liferay.portlet.configuration.web (Maven): affected all versions; fixed in 4.0.13 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-2021-33327/ (Markdown: https://insights.sbomify.com/CVE-2021-33327/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-33327 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-33327 - OSV: https://osv.dev/vulnerability/CVE-2021-33327 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-33327/ Summaries are generated and may contain mistakes; the official description above is the record.