# CVE-2020-7934: Liferay Portal Vulnerable to Persistent Cross-Site Scripting (XSS) in MyAccountPortlet

> Persistent XSS in Liferay Portal allows attackers to inject scripts via user name fields, potentially leading to session hijacking or malicious actions when users search for others.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 28 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f99h-h678-fgg4

## What is CVE-2020-7934?

CVE-2020-7934 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 28 Jan 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In LifeRay Portal CE 7.1.0 through 7.2.1 GA2, the First Name, Middle Name, and Last Name fields for user accounts in MyAccountPortlet are all vulnerable to a persistent XSS issue. Any user can modify these fields with a particular XSS payload, and it will be stored in the database. The payload will then be rendered when a user utilizes the search feature to search for other users (i.e., if a user with modified fields occurs in the search results). This issue was fixed in Liferay Portal CE version 7.3.0 GA1.

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

## Which versions are affected by CVE-2020-7934?

2 open source packages ship an affected version, including com.liferay.portal:release.portal.bom. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.1.0 | 7.3.0 |
| `com.liferay.portal:release.portal.bom` | Maven | From 7.1.0 | 7.3.0 |

Products: Liferay Liferay Portal.

## How do I fix CVE-2020-7934?

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

## Is CVE-2020-7934 being exploited?

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

Public exploit code:

- Authenticated Stored XSS in LifeRay 7.2.0 GA1 via MyAccountPortlet executed by Search Results (github_poc): https://github.com/3ndG4me/liferay-xss-7.2.1GA2-poc-report-CVE-2020-7934
- LifeRay 7.2.1 GA2 - Stored XSS (exploitdb)
- https://github.com/giardinas-dev/audit-xss-cve-2020-7934 (github_poc): https://github.com/giardinas-dev/audit-xss-cve-2020-7934

## 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-2020-7934 and fix it if it is affected.

What it is: CVE-2020-7934 is a medium-severity cross-site scripting vulnerability in Liferay Liferay Portal, published on 28 Jan 2020. 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-2020-7934 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.3.0
- com.liferay.portal:release.portal.bom (Maven): affected from 7.1.0; fixed in 7.3.0

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

## Sources

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

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