# CVE-2022-42130: Incorrect Default Permissions in Liferay Portal

> Remote authenticated users can view all form entries due to missing permission checks in the Dynamic Data Mapping module.

- **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:** 15 Nov 2022
- **Updated:** 9 Jul 2026
- **Also known as:** BIT-liferay-2022-42130, GHSA-mxvq-cv4x-p3jw

## What is CVE-2022-42130?

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

### Official description

The Dynamic Data Mapping module in Liferay Portal 7.1.0 through 7.4.3.4, and Liferay DXP 7.1 before fix pack 27, 7.2 before fix pack 19, 7.3 before update 4, and 7.4 GA does not properly check permission of form entries, which allows remote authenticated users to view and access all form entries.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-42130?

3 open source packages ship an affected version, including com.liferay.portal:release.portal.bom and liferay. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.1.0 | 7.4.3.5 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.1.0 | 7.4.3.5 |
| `liferay` | Bitnami | From 7.1.0 to 7.1.0 | None |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

## How do I fix CVE-2022-42130?

Upgrade com.liferay.portal:release.portal.bom to 7.4.3.5 or later.

## Is CVE-2022-42130 being exploited?

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

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

Affected packages and fixed versions:
- com.liferay.portal:release.portal.bom (Maven): affected from 7.1.0; fixed in 7.4.3.5
- com.liferay.portal:release.portal.bom (Maven): affected from 7.1.0; fixed in 7.4.3.5
- liferay (Bitnami): affected from 7.1.0 up to 7.1.0; 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-2022-42130/ (Markdown: https://insights.sbomify.com/CVE-2022-42130/index.md)
```

## Sources

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

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