# CVE-2023-42628: Liferay Portal and Liferay DXP Vulnerable to XSS in the Wiki Widget

> Remote attackers can inject arbitrary scripts into Liferay Wiki pages, potentially leading to session hijacking or malicious actions.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** BIT-liferay-2023-42628, GHSA-hv45-r2f5-fmhj

## What is CVE-2023-42628?

CVE-2023-42628 is a critical cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 17 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Stored cross-site scripting (XSS) vulnerability in the Wiki widget in Liferay Portal 7.1.0 through 7.4.3.87, and Liferay DXP 7.0 fix pack 83 through 102, 7.1 fix pack 28 and earlier, 7.2 fix pack 20 and earlier, 7.3 update 33 and earlier, and 7.4 before update 88 allows remote attackers to inject arbitrary web script or HTML into a parent wiki page via a crafted payload injected into a wiki page's ‘Content’ text field.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.10.fp83 to 7.0.10.fp102 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.0.10.fp83 to 7.0.10.fp102 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 to 7.1.10.fp28 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.1.0 to 7.1.10.fp28 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 to 7.2.10.fp20 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.2.0 to 7.2.10.fp20 | None |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u34 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.u34 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.0 | 7.4.13.u88 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.4.0 | 7.4.13.u88 |
| `liferay` | Bitnami | From 7.0.0 to 7.0.0 | None |
| `com.liferay:com.liferay.wiki.web` | Maven | All versions | 7.0.95 |
| `com.liferay:com.liferay.wiki.web` | Maven | All versions | 7.0.95 |

Products: Liferay Digital Experience Platform, Liferay Liferay Portal.

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

Upgrade com.liferay.portal:release.dxp.bom to a fixed version for your release line: 7.3.10.u34 or 7.4.13.u88.

## Is CVE-2023-42628 being exploited?

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

What it is: CVE-2023-42628 is a critical cross-site scripting vulnerability in Liferay Digital Experience Platform, published on 17 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-42628 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.fp83 up to 7.0.10.fp102; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.0.10.fp83 up to 7.0.10.fp102; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0 up to 7.1.10.fp28; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.1.0 up to 7.1.10.fp28; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0 up to 7.2.10.fp20; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.2.0 up to 7.2.10.fp20; no fix listed
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u34
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.u34
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.0; fixed in 7.4.13.u88
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.4.0; fixed in 7.4.13.u88
- liferay (Bitnami): affected from 7.0.0 up to 7.0.0; no fix listed
- com.liferay:com.liferay.wiki.web (Maven): affected all versions; fixed in 7.0.95

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

## Sources

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

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