# CVE-2021-29052: Liferay Portal and Liferay DXP Fails to Check Permissions

> Authenticated users can bypass permission checks to view unauthorized DDMStructures via the Data Engine module API.

- **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:** 17 May 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-pr7v-qv65-rp9m

## What is CVE-2021-29052?

CVE-2021-29052 is a medium-severity missing authorization vulnerability in Liferay Liferay Portal, published on 17 May 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Data Engine module in Liferay Portal 7.3.0 through 7.3.5, and Liferay DXP 7.3 before fix pack 1 does not check permissions in DataDefinitionResourceImpl.getSiteDataDefinitionByContentTypeByDataDefinitionKey, which allows remote authenticated users to view DDMStructures via GET API calls.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2021-29052?

4 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 | All versions | 7.3.10.fp1 |
| `com.liferay.portal:release.dxp.bom` | Maven | All versions | 7.3.10.fp1 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.3.0 to 7.3.5 | None |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.3.0 to 7.3.5 | None |

Products: Liferay Dxp, Liferay Liferay Portal.

## How do I fix CVE-2021-29052?

Upgrade com.liferay.portal:release.dxp.bom to 7.3.10.fp1 or later.

## Is CVE-2021-29052 being exploited?

There is no known exploitation of CVE-2021-29052 in the wild and no public exploit code.

## Other vulnerabilities in Liferay Liferay Portal

- [CVE-2022-42120](https://insights.sbomify.com/CVE-2022-42120/): Liferay Portal and Liferay DXP Vulnerable to SQL Injection via the Fragment Module (critical 9.8)
- [CVE-2022-42122](https://insights.sbomify.com/CVE-2022-42122/): Liferay Portal and Liferay DXP Vulnerable to SQL Injection via Friendly URL Module (critical 9.8)
- [CVE-2023-35030](https://insights.sbomify.com/CVE-2023-35030/): Liferay Portal and Liferay DXP Vulnerable to CSRF via the Layout Module (high 8.8)
- [CVE-2021-29053](https://insights.sbomify.com/CVE-2021-29053/): Liferay Portal and Liferay DXP Vulnerable to Multiple SQL Injections (high 8.8)
- [CVE-2021-33321](https://insights.sbomify.com/CVE-2021-33321/): Liferay Portal and Liferay DXP insecure default configuration (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29052 and fix it if it is affected.

What it is: CVE-2021-29052 is a medium-severity missing authorization vulnerability in Liferay Liferay Portal, published on 17 May 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-29052 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected all versions; fixed in 7.3.10.fp1
- com.liferay.portal:release.dxp.bom (Maven): affected all versions; fixed in 7.3.10.fp1
- com.liferay.portal:release.portal.bom (Maven): affected from 7.3.0 up to 7.3.5; no fix listed
- com.liferay.portal:release.portal.bom (Maven): affected from 7.3.0 up to 7.3.5; no fix listed

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

## Sources

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

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