# CVE-2022-38512: Liferay Portal and Liferay DXP Fails to Check Permissions in Translation Module

> Attackers can download web content translation files without proper permission checks, exposing sensitive content data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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:** 22 Sep 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-h9ww-wjg4-jvvg

## What is CVE-2022-38512?

CVE-2022-38512 is a medium-severity missing authorization vulnerability in Liferay Liferay Portal, published on 22 Sep 2022. 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

The Translation module in Liferay Portal v7.4.3.12 through v7.4.3.36, and Liferay DXP 7.4 update 8 through 36 does not check permissions before allowing a user to export a web content for translation, allowing attackers to download a web content page's XLIFF translation file via crafted URL.

Weakness: CWE-862 (Missing Authorization)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u8 | 7.4.13.u37 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u8 | 7.4.13.u37 |
| `com.liferay:com.liferay.translation.web` | Maven | All versions | 2.0.58 |
| `com.liferay:com.liferay.translation.web` | Maven | All versions | 2.0.58 |

Products: Liferay Dxp, Liferay Liferay Portal.

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

Upgrade com.liferay.portal:release.dxp.bom to 7.4.13.u37 or later.

## Is CVE-2022-38512 being exploited?

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

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

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.13.u8; fixed in 7.4.13.u37
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.13.u8; fixed in 7.4.13.u37
- com.liferay:com.liferay.translation.web (Maven): affected all versions; fixed in 2.0.58
- com.liferay:com.liferay.translation.web (Maven): affected all versions; fixed in 2.0.58

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

## Sources

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

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