Liferay Portal Vulnerable to Persistent Cross-Site Scripting (XSS) in MyAccountPortlet

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2020-7934: 4.49% estimated exploitation activity in the next 30 days; percentile 91.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

In LifeRay Portal CE 7.1.0 through 7.2.1, 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).

Published by the source

24 May 2022, 17:07 UTC

Last modified by the source

28 Apr 2025, 19:21 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f99h-h678-fgg4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2020-7934

Advisory: Liferay Portal Vulnerable to Persistent Cross-Site Scripting (XSS) in MyAccountPortlet
IDs: CVE-2020-7934, GHSA-f99h-h678-fgg4
Record: https://patchnext.com/advisories/cve-2020-7934 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.liferay.portal:release.portal.bom 7.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.liferay.portal:release.portal.bom: affected >= 7.1.0, <= 7.2.1; fixed in 7.3.0

## Suggested inspection (read-only)
- Maven com.liferay.portal:release.portal.bom: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.liferay.portal:release.portal.bom.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f99h-h678-fgg4 (GitHub-reviewed advisory GHSA-f99h-h678-fgg4 lists affected ranges: Maven com.liferay.portal:release.portal.bom >=7.1.0 <=7.2.1)

Commands are suggestions: review each one before running it.