# CVE-2022-26594: Liferay Portal and Liferay DXP allows arbitrary injection via form field

> Remote attackers can inject arbitrary web script or HTML via form field help text in Liferay Portal's Forms and App Builder modules.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 15 Apr 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-658f-xhv4-p978

## What is CVE-2022-26594?

CVE-2022-26594 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 15 Apr 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

Multiple cross-site scripting (XSS) vulnerabilities in Liferay Portal 7.3.5 through 7.4.0, and Liferay DXP 7.3 before service pack 3 allow remote attackers to inject arbitrary web script or HTML via a form field's help text to (1) Forms module's form builder, or (2) App Builder module's object form view's form builder.

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

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

4 open source packages ship an affected version, including com.liferay.portal:release.dxp.bom and com.liferay:com.liferay.dynamic.data.mapping.form.field.type. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.fp3 |
| `com.liferay.portal:release.dxp.bom` | Maven | From 7.3.0 | 7.3.10.fp3 |
| `com.liferay:com.liferay.dynamic.data.mapping.form.field.type` | Maven | All versions | 6.0.11 |
| `com.liferay:com.liferay.dynamic.data.mapping.form.field.type` | Maven | All versions | 6.0.11 |

Products: Liferay Liferay Portal.

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

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

## Is CVE-2022-26594 being exploited?

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

## Other vulnerabilities in Liferay Liferay Portal

- [CVE-2020-7961](https://insights.sbomify.com/CVE-2020-7961/): Liferay Portal Deserialization of Untrusted Data (critical 9.8, exploited in the wild)
- [CVE-2021-33990](https://insights.sbomify.com/CVE-2021-33990/): File upload in n/a (critical 9.8)
- [CVE-2019-16891](https://insights.sbomify.com/CVE-2019-16891/): Liferay Portal Allows RCE via Deserialization of a JSON Payload (critical 9.8)
- [CVE-2023-47797](https://insights.sbomify.com/CVE-2023-47797/): Liferay Portal XSS with `p_l_back_url_title` on edit content page (critical 9.6)
- [CVE-2020-13445](https://insights.sbomify.com/CVE-2020-13445/): Liferay Portal and Liferay DXP Vulnerable to Arbitrary Code Execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26594 and fix it if it is affected.

What it is: CVE-2022-26594 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 15 Apr 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-26594 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.fp3
- com.liferay.portal:release.dxp.bom (Maven): affected from 7.3.0; fixed in 7.3.10.fp3
- com.liferay:com.liferay.dynamic.data.mapping.form.field.type (Maven): affected all versions; fixed in 6.0.11
- com.liferay:com.liferay.dynamic.data.mapping.form.field.type (Maven): affected all versions; fixed in 6.0.11

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

## Sources

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

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