# CVE-2023-35030: Liferay Portal and Liferay DXP Vulnerable to CSRF via the Layout Module

> Attackers can exploit CSRF in Liferay Portal to execute arbitrary code in the scripting console via a crafted backURL parameter.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 15 Jun 2023
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-p2fc-xxr8-fw3p

## What is CVE-2023-35030?

CVE-2023-35030 is a high-severity vulnerability in Liferay Liferay Portal, published on 15 Jun 2023. 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

Cross-site request forgery (CSRF) vulnerability in the Layout module's SEO configuration in Liferay Portal 7.4.3.70 through 7.4.3.76, and Liferay DXP 7.4 update 70 through 76 allows remote attackers to execute arbitrary code in the scripting console via the `_com_liferay_layout_admin_web_portlet_GroupPagesPortlet_backURL` parameter.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

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 | From 7.4.13.u70 to 7.4.13.u76 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.13.u70 to 7.4.13.u76 | None |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.70-ga70 | 7.4.3.77-ga77 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.4.3.70-ga70 | 7.4.3.77-ga77 |

Products: Liferay Dxp, Liferay Liferay Portal.

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

Apply the vendor's patch.

## Is CVE-2023-35030 being exploited?

There is no known exploitation of CVE-2023-35030 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-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)
- [CVE-2021-29047](https://insights.sbomify.com/CVE-2021-29047/): Liferay Portal and Liferay DXP Fails to Invalidate CAPTCHA Answers After Use (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-35030 and fix it if it is affected.

What it is: CVE-2023-35030 is a high-severity vulnerability in Liferay Liferay Portal, published on 15 Jun 2023. 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-2023-35030 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.u70 up to 7.4.13.u76; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.13.u70 up to 7.4.13.u76; no fix listed
- com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.70-ga70; fixed in 7.4.3.77-ga77
- com.liferay.portal:release.portal.bom (Maven): affected from 7.4.3.70-ga70; fixed in 7.4.3.77-ga77

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

## Sources

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

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